Loading vulnerability…
CVE-2006-6183 is a stack-based buffer overflow vulnerability in 3Com 3CTftpSvc version 2.0.1 and possibly earlier. The vulnerability exists in the handling of the 'mode' field in TFTP GET and PUT commands, where an overly long value can overflow a stack buffer, potentially allowing remote attackers to crash the service or 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 (4 hidden).
This repository contains a single Metasploit module targeting a stack buffer overflow vulnerability in 3CTftpSvc version 2.0.1 (CVE-2006-6183) on Windows. The exploit works by sending a specially crafted TFTP packet with an overly long 'mode' field to UDP port 69, triggering a buffer overflow and allowing execution of arbitrary code. The module allows the user to select a payload (up to 400 bytes, avoiding null bytes), which will be executed on the target system if the exploit is successful. The code is written in Ruby and follows the standard Metasploit module structure, utilizing the Msf::Exploit::Remote::Udp mixin for network communication. The only endpoint involved is the TFTP service on UDP port 69. The exploit is operational and can be used to gain remote code execution on vulnerable systems.
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.