CVE-2010-3350 json
bareFTP 0.3.4 places a zero-length directory name in the LD_LIBRARY_PATH, which allows local users to gain privileges via a Trojan horse sh…
published 2010-10-20 16 y ago modified 2026-06-16 4 mo ago also EUVD-2010-3348
- cvss
- 6.9
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 24%
- public exploits
- 0
- none known
Summary
bareFTP 0.3.4 places a zero-length directory name in the LD_LIBRARY_PATH, which allows local users to gain privileges via a Trojan horse shared library in the current working directory.
Patch / fix
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-3350 updated cvss 3.7
bareftp: insecure library loading vulnerability
-
Red Hat All currently supported Red Hat productsnot 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
0.32% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.9 | AV:L/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
bugs.debian.org
/cgi-bin/bugreport.cgi?bug=598284
patch
-
lists.fedoraproject.org
/pipermail/package-announce/2010-December/051936.html
vendor-advisory
-
lists.fedoraproject.org
/pipermail/package-announce/2010-December/051921.html
vendor-advisory
-
vupen.com
/english/advisories/2010/3141
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/64433
vdb-entry
-
secunia.com
/advisories/42521
third-party-advisory
- gitorious.org /bareftp/bareftp/blobs/15489abdb4c698cf832e95184bfe769a1ba70238/ChangeLog
-
securityfocus.com
/bid/44334
vdb-entry
Sources
- CVE List CVE-2010-3350
- NVD CVE-2010-3350
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.