Loading vulnerability…
A stack-based buffer overflow exists in the AntServer Module (AntServer.exe) of BigAnt IM Server version 2.50. The vulnerability is triggered by sending a specially crafted, overly long GET request to TCP port 6660, which can overwrite the stack and 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 (2 hidden).
This repository contains a single Metasploit exploit module targeting a stack buffer overflow vulnerability in the BigAnt Server 2.52 Messaging Service (CVE-2009-4660). The exploit connects to the AntServer service on TCP port 6660, crafts a specially encoded buffer containing user-supplied shellcode, and sends it using the 'USV' command to trigger the overflow. The buffer is XOR-encoded as required by the protocol. The exploit allows for arbitrary code execution with the privileges of the AntServer service. The module is operational and allows the attacker to select any Metasploit payload, such as a reverse shell. The exploit is single-use per service start, as the AntServer does not restart after exploitation. The code is written in Ruby and is structured as a standard Metasploit module, with all relevant exploit logic contained in the 'exploit' method.
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.