CVE-2008-1620 json
Directory traversal vulnerability in 2X TFTP service (TFTPd.exe) 3.2.0.0 and earlier in 2X ThinClientServer 5.0_sp1-r3497 and earlier allow…
published 2008-04-02 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-1621
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.0%
- EPSS 3.0% chance of exploitation in 30 days, percentile 87%
- public exploits
- 1
- Exploit-DB
Summary
Directory traversal vulnerability in 2X TFTP service (TFTPd.exe) 3.2.0.0 and earlier in 2X ThinClientServer 5.0_sp1-r3497 and earlier allows remote attackers to read or overwrite arbitrary files via a ... (dot dot dot) in the filename.
Patch / fix
Timeline
- First public exploit (EDB-31562)
- Published
Exploit prediction
3.03% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-31562 2X ThinClientServer 5.0 sp1-r3497 TFTP Service - Directory Traversal remote, 2008-03-29
- aluigi.org http://aluigi.org/testz/tftpx.zip referenced PoC, tagged "exploit" by a source, unverified
- aluigi.altervista.org http://aluigi.altervista.org/adv/thindirtrav-adv.txt referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
aluigi.org
/testz/tftpx.zip
exploit, patch
-
aluigi.altervista.org
/adv/thindirtrav-adv.txt
exploit
-
secunia.com
/advisories/29590
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/41528
vdb-entry
-
securityfocus.com
/archive/1/490324/100/0/threaded
mailing-list
-
vupen.com
/english/advisories/2008/1040/references
vdb-entry
-
securityfocus.com
/bid/28504
vdb-entry
Sources
- CVE List CVE-2008-1620
- NVD CVE-2008-1620
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.