CVE-2005-1812 in the critical feed json
Multiple stack-based buffer overflows in FutureSoft TFTP Server Evaluation Version 1.0.0.1 allow remote attackers to execute arbitrary code…
published 2005-06-01 21 y ago modified 2026-06-16 4 mo ago also EUVD-2005-1814
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 62.9%
- EPSS 62.9% chance of exploitation in 30 days, percentile 99.2%
- public exploits
- 3
- Metasploit, Exploit-DB
Summary
Multiple stack-based buffer overflows in FutureSoft TFTP Server Evaluation Version 1.0.0.1 allow remote attackers to execute arbitrary code via a long (1) filename or (2) transfer mode string in a Read Request (RRQ) or Write Request (WRQ) packet.
Timeline
- First public exploit (Metasploit exploit/windows/tftp/futuresoft_transfermode)
- Published
Exploit prediction
62.92% chance of exploitation in the next 30 days, higher than 99.2% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Metasploit exploit/windows/tftp/futuresoft_transfermode FutureSoft TFTP Server 2000 Transfer-Mode Overflow metasploit exploit, average rank, 2005-05-31
- EDB-16344 FutureSoft TFTP Server 2000 - Transfer-Mode Overflow (Metasploit) remote, 2010-05-09
- EDB-1027 FutureSoft TFTP Server 2000 - Remote Denial of Service dos, 2005-06-02
- securityfocus.com http://www.securityfocus.com/bid/13821 referenced PoC, tagged "exploit" by a source, unverified
- security.org.sg http://www.security.org.sg/vuln/tftp2000-1001.html 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-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
securityfocus.com
/bid/13821
vdb-entry, exploit
-
security.org.sg
/vuln/tftp2000-1001.html
exploit
-
secunia.com
/advisories/15539
third-party-advisory
-
securitytracker.com
/id?1014079
vdb-entry
Sources
- CVE List CVE-2005-1812
- NVD CVE-2005-1812
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.