Loading vulnerability…
BigAntSoft BigAnt IM Message Server does not require authentication for file upload functionality, allowing a remote unauthenticated attacker to upload content and create arbitrary files under the server-side path AntServer\DocData\Public via unspecified vectors. This is an access control/authentication failure on a file upload endpoint, enabling attacker-controlled file creation within a publicly accessible document storage directory.
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 (modules/exploits/windows/misc/bigant_server_dupf_upload.rb) that exploits an unauthenticated arbitrary file upload vulnerability in BigAnt Server 2.97 SP7 (CVE-2012-6274). The exploit leverages the DUPF command on TCP port 6661 to upload files to arbitrary locations on the server, including the Windows system directories. By uploading a malicious executable and a specially crafted MOF file to the wbem\mof directory, the module triggers Windows Management Instrumentation (WMI) to execute the payload as SYSTEM. The exploit is operational and provides remote code execution capabilities. The code is written in Ruby and is designed to be used within the Metasploit Framework. No hardcoded IPs or domains are present, but the exploit targets the default BigAnt Server port (6661) and specific file paths on the Windows filesystem.
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.