Loading vulnerability…
TFTP Server SP versions 1.4 and 1.5 on Windows contain a buffer overflow when processing an overly long TFTP error packet. A remote attacker can exploit the overflow to execute arbitrary code. Other affected versions may exist, but are not confirmed.
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: 'OpenTFTP SP 1.4 Error Packet Overflow'. The exploit targets a buffer overflow vulnerability in OpenTFTP Server SP 1.4 running on Windows. The flaw is triggered by sending a specially crafted TFTP error packet (opcode 0x05) to the server's UDP port 69. The vulnerable server uses sprintf() to format the error message, leading to a stack buffer overflow and allowing remote code execution as SYSTEM. The module supports both 'Service' and 'Stand Alone' modes of the TFTP server, with different offsets for each. The exploit is fully integrated into Metasploit, allowing the user to select and deliver a payload (such as a reverse shell) to the target. The only fingerprintable endpoint is the TFTP service on UDP port 69. The code is operational and weaponized for use within 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.