FutureSoft TFTP Server Evaluation Version 1.0.0.1 contains multiple stack-based buffer overflows when processing TFTP Read Request (RRQ) and Write Request (WRQ) packets. An overly long filename or transfer-mode string can overflow stack memory and allow a remote attacker to execute arbitrary code.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a Metasploit exploit module targeting a stack buffer overflow vulnerability in FutureSoft TFTP Server 2000 (CVE-2005-1812). The exploit works by sending a specially crafted TFTP request with an overly long transfer-mode string to the server's UDP port 69, causing a buffer overflow that overwrites the Structured Exception Handler (SEH) and saved EIP. The module allows the attacker to execute arbitrary code (Metasploit payloads up to 350 bytes) on the target system with the privileges of the TFTP server process. The exploit is operational and supports multiple Windows targets, with specific return addresses for each. The only network endpoint involved is UDP port 69, the standard TFTP port. The code is written in Ruby and is structured as a typical Metasploit module, with all logic contained in a single file.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.