A stack-based buffer overflow exists in TinyIdentD version 2.2 and earlier. The vulnerability is triggered when a remote attacker sends a long string to TCP port 113, which is not properly bounds-checked, resulting in a buffer overflow on the stack. This can allow the attacker to overwrite the return address and execute arbitrary code with the privileges of the TinyIdentD process.
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 exploit module targeting a stack-based buffer overflow vulnerability in TinyIdentD version 2.2 (CVE-2007-2711). The exploit is designed for Windows platforms (Windows 2000 and Windows XP, various language editions) and abuses the identd service running on TCP port 113. By sending a specially crafted, overly long request to the identd service, the exploit overwrites the return address on the stack, allowing arbitrary code execution. The module supports customizable payloads up to 450 bytes, with certain bad characters filtered out. The exploit is operational and can be used to gain code execution on vulnerable systems. The repository structure is typical for a Metasploit module, with all logic contained in a single Ruby file implementing the exploit.
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.