CVE-2010-4148 json
Directory traversal vulnerability in AnyConnect 1.2.3.0, and possibly earlier, allows remote FTP servers to write arbitrary files via a "..…
published 2010-11-01 16 y ago modified 2026-06-16 4 mo ago also EUVD-2010-4124
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.8%
- EPSS 1.8% chance of exploitation in 30 days, percentile 78%
- public exploits
- 0
- none known
Summary
Directory traversal vulnerability in AnyConnect 1.2.3.0, and possibly earlier, allows remote FTP servers to write arbitrary files via a "..\" (dot dot backslash) in a filename.
Exploit prediction
1.76% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- htbridge.ch http://www.htbridge.ch/advisory/directory_traversal_vulnerability_in_anyconnect.html referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.org http://packetstormsecurity.org/1010-exploits/anyconnect-traversal.txt referenced PoC, tagged "exploit" by a source, unverified
- marc.info http://marc.info/?l=bugtraq&m=128699692209082&w=2 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
htbridge.ch
/advisory/directory_traversal_vulnerability_in_anyconnect.html
exploit
-
packetstormsecurity.org
/1010-exploits/anyconnect-traversal.txt
exploit
-
marc.info
/?l=bugtraq&m=128699692209082&w=2
mailing-list, exploit
-
secunia.com
/advisories/41802
third-party-advisory, vendor-advisory
-
osvdb.org
/68666
vdb-entry
-
securityfocus.com
/bid/44076
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/62563
vdb-entry
Sources
- CVE List CVE-2010-4148
- NVD CVE-2010-4148
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.