Loading vulnerability…
A stack-based buffer overflow exists in TFTP Server SP 1.4 for Windows. The vulnerability is triggered when a remote attacker sends a read or write request containing an excessively long filename, which overflows a stack buffer and can lead to denial of service or arbitrary code execution.
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 (2 hidden).
This repository contains a single Metasploit exploit module targeting a buffer overflow vulnerability (CVE-2008-1611) in TFTP Server 1.4 ST for Windows. The exploit abuses improper bounds checking in the handling of WRQ (Write Request) filenames, allowing an attacker to send a specially crafted UDP packet to port 69, resulting in remote code execution. The module supports multiple targets, including Windows XP and Windows 7 (both x86 and x64), and requires the attacker to know whether the TFTP server is running as a service or standalone to select the correct offset. The payload is customizable via the Metasploit framework and can execute with SYSTEM or user privileges depending on the TFTP server's context. The only fingerprintable endpoint is UDP port 69, the standard TFTP port. The exploit is operational and not a mere proof-of-concept, as it delivers a working payload and is integrated into the Metasploit framework.
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.