Loading vulnerability…
A stack-based buffer overflow exists in Sysax Multi Server versions prior to 5.52 when the HTTP service is enabled. The vulnerability can be triggered by remote authenticated users with the 'create folder' permission, who can send a specially crafted HTTP request to overflow a stack buffer, leading to potential 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 module (Ruby file) that exploits a stack buffer overflow vulnerability in the 'create folder' function of Sysax Multi Server 5.64 (CVE-2012-6530). The exploit targets Windows XP SP3 and Windows Server 2003 SP1-SP2 systems where the HTTP interface is enabled. The module requires valid credentials with folder creation permissions. It works by logging in to obtain a session ID (SID), determining the root folder path, and then sending a specially crafted HTTP POST request to the vulnerable endpoint to trigger the overflow. The payload is customizable via Metasploit and, if successful, results in SYSTEM-level code execution. The file structure is typical for a Metasploit exploit module, and the code leverages Metasploit's HttpClient mixin for network communication. The endpoints used are all HTTP requests to the Sysax server's '/scgi' path with various parameters for login, folder path discovery, and exploitation.
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.