Loading vulnerability…
CVE-2012-6275 describes multiple stack-based buffer overflows in AntDS.exe, a component of BigAntSoft BigAnt IM Message Server. The vulnerabilities are triggered by sending specially crafted requests: (1) a SCH request with a malicious filename header, or (2) a DUPF request with a malicious userid component. These inputs are not properly bounds-checked, leading to buffer overflows on the stack.
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 module (Ruby file) that exploits a stack buffer overflow vulnerability (CVE-2012-6275) in BigAnt Server 2.97 SP7. The exploit targets the server's TCP service (default port 6661) by sending specially crafted SCH and DUPF requests, triggering a buffer overflow via unsafe strcpy usage. The module supports two targets: Windows XP SP3 and Windows 2003 SP2, with specific return addresses and a ROP chain for Windows 2003. The payload is customizable (up to 2500 bytes) and can execute arbitrary code, such as a reverse shell, with SYSTEM privileges. The exploit is operational and requires the attacker to specify the target's IP and ensure the service is accessible. The repository is structured as a standard Metasploit exploit module, with all logic contained in a single Ruby file.
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.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.