CVE-2008-0405 json
Multiple directory traversal vulnerabilities in HTTP File Server (HFS) before 2.2c, when account names are used as log filenames, allow rem…
published 2008-01-28 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-0415
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.1%
- EPSS 3.1% chance of exploitation in 30 days, percentile 87%
- public exploits
- 0
- none known
Summary
Multiple directory traversal vulnerabilities in HTTP File Server (HFS) before 2.2c, when account names are used as log filenames, allow remote attackers to create arbitrary (1) files and (2) directories via a .. (dot dot) in an account name, when requesting the / URI; and (3) append arbitrary data to a file via a .. (dot dot) in an account name, when requesting a URI composed of a "/?%0a" sequence followed by the data.
Exploit prediction
3.07% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- rejetto.com http://www.rejetto.com/hfs/?f=wn referenced PoC, tagged "exploit" by a source, unverified
- syhunt.com http://www.syhunt.com/advisories/hfshack.txt referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
rejetto.com
/hfs/?f=wn
exploit
-
syhunt.com
/advisories/hfshack.txt
exploit
-
secunia.com
/advisories/28631
third-party-advisory, vendor-advisory
-
securityfocus.com
/bid/27423
vdb-entry
-
securityreason.com
/securityalert/3581
third-party-advisory
-
securityfocus.com
/archive/1/486873/100/0/threaded
mailing-list
- syhunt.com /advisories/hfs-1-log.txt
-
exchange.xforce.ibmcloud.com
/vulnerabilities/39873
vdb-entry
Sources
- CVE List CVE-2008-0405
- NVD CVE-2008-0405
Fencer Vulns 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.