Loading vulnerability…
A buffer overflow vulnerability exists in the FTP service of 3Com 3CDaemon 2.0 revision 10. The vulnerability can be triggered by sending a long username in the USER command or by issuing FTP commands (such as cd, send, or ls) with excessively long arguments. This can result in a denial of service (application crash) or potentially allow remote attackers to execute arbitrary code on the affected system.
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-2005-0277) in the 3Com 3CDaemon FTP Server version 2.0. The exploit works by sending a specially crafted USER command to the FTP service, overflowing the buffer and allowing arbitrary code execution. The module supports multiple Windows targets, including Windows 2000, Windows XP (various service packs), and Windows NT 4.0. The payload is customizable and delivered via the Metasploit framework, with a maximum size of 674 bytes and specific bad characters to avoid. The exploit requires network access to the target's FTP service (typically on TCP port 21). The repository structure is typical for a Metasploit module, with all logic contained in a single Ruby file implementing the exploit, payload delivery, and target selection.
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.