CVE-2010-2426 json
Directory traversal vulnerability in TitanFTPd in South River Technologies Titan FTP Server 8.10.1125, and probably earlier versions, allow…
published 16y ago modified 4mo ago also EUVD-2010-2435
- cvss
- 4.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 12.3%
- EPSS 12.3% chance of exploitation in 30 days, percentile 96%
- public exploits
- 1
- Metasploit
Summary
Directory traversal vulnerability in TitanFTPd in South River Technologies Titan FTP Server 8.10.1125, and probably earlier versions, allows remote authenticated users to read arbitrary files, determine file size, via "..//" sequences in the xcrc command.
Is CVE-2010-2426 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 FencerTimeline
- First public exploit (Metasploit auxiliary/scanner/ftp/titanftp_xcrc_traversal)
- Published
Exploit prediction
12.26% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit auxiliary/scanner/ftp/titanftp_xcrc_traversal Titan FTP XCRC Directory Traversal Information Disclosure metasploit auxiliary, normal rank, 2010-06-15
- securityfocus.com http://www.securityfocus.com/bid/40949 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
securityfocus.com
/bid/40949
vdb-entry, exploit
-
secunia.com
/advisories/40237
third-party-advisory, vendor-advisory
-
osvdb.org
/65533
vdb-entry
-
securityfocus.com
/archive/1/511839/100/0/threaded
mailing-list
-
exchange.xforce.ibmcloud.com
/vulnerabilities/59492
vdb-entry
Sources
- CVE List CVE-2010-2426
- NVD CVE-2010-2426
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.