Skip to content
Noroxi
CVE-2010-2251· NVD / CVE Program· CNA mitre

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

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.

HighCVSS 7.5 · v2.0—No exploit Fix available
Published
Jul 6, 2010
Updated
Jun 16, 2026
EPSS
3.6% · 89th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 3.6%

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

VendorProduct
alexander v. lukyanovlftp

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • alexander v. lukyanov lftpup to 4.0.5 inclusive
  • alexander v. lukyanov lftp2.0.0
  • alexander v. lukyanov lftp2.0.1
  • alexander v. lukyanov lftp2.0.2
  • alexander v. lukyanov lftp2.0.3
  • alexander v. lukyanov lftp2.0.4
  • alexander v. lukyanov lftp2.0.5
  • alexander v. lukyanov lftp2.1.0
  • alexander v. lukyanov lftp2.1.1
  • alexander v. lukyanov lftp2.1.10
  • alexander v. lukyanov lftp2.1.2
  • alexander v. lukyanov lftp2.1.3
  • alexander v. lukyanov lftp2.1.4
  • alexander v. lukyanov lftp2.1.5
  • alexander v. lukyanov lftp2.1.6
  • alexander v. lukyanov lftp2.1.7
  • alexander v. lukyanov lftp2.1.8
  • alexander v. lukyanov lftp2.1.9
  • alexander v. lukyanov lftp2.2.0
  • alexander v. lukyanov lftp2.2.0a

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12lftpbefore 4.0.6-14.0.6-1
Debian:5.0lftpbefore 3.7.3-1+lenny13.7.3-1+lenny1
Red Hat:enterprise_linux:5::clientlftpbefore 0:3.7.11-4.el5_5.30:3.7.11-4.el5_5.3
Red Hat:enterprise_linux:5::clientlftp-debuginfobefore 0:3.7.11-4.el5_5.30:3.7.11-4.el5_5.3

Other highest-scoring records for the same primary product.

  • CVE-2003-0963Buffer overflows in (1) try_netscape_proxy and (2) try_squid_eplf for lftp 2.6.9 and earlier allow remote HTTP servers to execute arbitrary
    34Monitor
  • CVE-2007-2348mirror --script in lftp before 3.5.9 does not properly quote shell metacharacters, which might allow remote user-assisted attackers to execu
    28Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:lftp4.0.6-1 · Debian:12Package registry (OSV)
red hat:lftp0:3.7.11-4.el5_5.3 · Red Hat:enterprise_linux:5::clientPackage registry (OSV)
red hat:lftp-debuginfo0:3.7.11-4.el5_5.3 · Red Hat:enterprise_linux:5::clientPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records