CVE-2005-1815 describes multiple buffer overflow vulnerabilities in Hummingbird Connectivity inetD versions 10.0.0.1 and 9.0.0.4. The vulnerabilities exist in the FTPD (ftpdw.exe) and LPD (Lpdw.exe) components. Specifically, an attacker can trigger a buffer overflow by sending an FTP command with an excessively long argument to FTPD or by sending a large amount of data to LPD. These overflows can result in a denial of service and potentially allow for arbitrary code execution.
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.
This repository contains a single Metasploit exploit module targeting a stack buffer overflow vulnerability (CVE-2005-1815) in the Hummingbird Connectivity Exceed v10 SP5 LPD Daemon. The exploit is designed for Windows 2000 (SP0-SP4) and Windows XP (SP0/SP1) systems running the vulnerable LPD service on TCP port 515. The module constructs a specially crafted payload to overflow the buffer and overwrite the SEH (Structured Exception Handler), allowing execution of arbitrary code with the privileges of the LPD service. The payload is customizable via Metasploit and can be up to 500 bytes, excluding null bytes and line feeds. The exploit is operational and provides remote code execution capabilities. The only fingerprintable endpoint is the LPD service on TCP port 515. The code is written in Ruby and follows the standard Metasploit module structure.
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.