Skip to content
Fencer Intel
high 7.5

CVE-2010-2251 json

The get1 command, as used by lftpget, in LFTP before 4.0.6 does not properly validate a server-provided filename before determining the des…

published 16y ago modified 4mo ago also EUVD-2010-2263

cvss
7.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.6%
EPSS 3.6% chance of exploitation in 30 days, percentile 89%
public exploits
0
none known

Summary

The get1 command, as used by lftpget, in LFTP before 4.0.6 does not properly validate a server-provided filename before determining the destination filename of a download, which allows remote servers to create or overwrite arbitrary files via a Content-Disposition header that suggests a crafted filename, and possibly execute arbitrary code as a consequence of writing to a dotfile in a home directory.

Patch / fix

  • lftp Debian 14, Debian 13, Debian 12 4.0.6-1

debian advisories DEBIAN-CVE-2010-2251

  • lftp RHEL 5 3.7.11-4.el5_5.3

red hat advisories RHSA-2010:0585

Is CVE-2010-2251 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2010-2251 updated cvss 5.8

lftp: multiple HTTP client download filename vulnerability [OCERT 2010-001]

  • Red Hat Enterprise Linux (v. 5 server) lftp 3.7.11-4.el5_5.3 Red Hat Enterprise Linux Desktop (v. 5 client) lftp 3.7.11-4.el5_5.3
    fixed: vendor fix RHSA-2010:0585
  • Red Hat Enterprise Linux 6 lftp, lftp-scripts
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

3.63% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.