Loading vulnerability…
A buffer overflow vulnerability exists in the tftpd component of TFTP32 versions 2.21 and earlier. The vulnerability is triggered when a remote attacker sends a TFTP request with an excessively long filename argument, causing a buffer overflow and potentially allowing the execution of 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 single Metasploit module (Ruby file) that exploits a stack buffer overflow vulnerability in TFTPD32 version 2.21 and prior (CVE-2002-2226). The exploit targets the TFTP service running on UDP port 69 on Windows NT 4.0 SP6a, Windows 2000 Pro SP4, and Windows XP Pro SP0/SP1. By sending a specially crafted TFTP request with an overly long filename, the exploit overflows a stack buffer, allowing arbitrary code execution with the privileges of the TFTP service. The module supports custom payloads via the Metasploit framework, enabling actions such as spawning a shell. The code is operational and leverages Metasploit's UDP and payload handling capabilities. No hardcoded IP addresses or file paths are present; the main fingerprintable endpoint is the TFTP UDP service on port 69.
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.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.