Loading vulnerability…
A stack-based buffer overflow exists in tftpd.exe in ProSysInfo TFTP Server TFTPDWIN 0.4.2 and earlier. The vulnerability is triggered when a remote attacker sends a TFTP request with an excessively long file name, causing a buffer overflow in the handling code. This can result in the execution of arbitrary code or a denial of service condition.
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 in ProSysInfo TFTPDWIN v0.4.2 (CVE-2006-4948). The exploit works by sending a specially crafted TFTP request with an overly long filename to the tftpd.exe server running on UDP port 69. This overflows the stack and allows for arbitrary code execution with the privileges of the TFTP service. The module is written in Ruby and leverages Metasploit's UDP and payload handling capabilities. The payload is customizable (up to 284 bytes, avoiding null bytes) and can be configured to provide a shell or other post-exploitation actions. The exploit is operational and has been tested on multiple Windows versions. No hardcoded IP addresses or domain names are present, but the exploit specifically targets the TFTP service on UDP 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.
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.