Loading vulnerability…
CVE-2012-10039 is a command injection vulnerability in ZEN Load Balancer versions 2.0 and 3.0-rc1. The flaw is present in content2-2.cgi, where the filelog parameter is incorporated directly into a backtick-delimited exec() call without proper sanitization or neutralization of shell metacharacters. Because user-controlled input reaches shell execution unsafely, an authenticated attacker can inject arbitrary operating system commands. The vulnerable product is the legacy predecessor to ZEVENET and SKUDONET, and the affected versions are no longer supported.
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 (zen_load_balancer_exec.rb) that exploits an authenticated command execution vulnerability (CVE-2012-10039) in ZEN Load Balancer versions 2.0 and 3.0-rc1. The exploit targets the 'filelog' parameter in the /index.cgi endpoint, which is vulnerable to command injection due to improper handling of user input. The module requires valid credentials (default: admin/admin) and sends a specially crafted request to execute arbitrary commands as root. The module also includes a check method that queries /config/global.conf to verify the target version. The exploit is operational and allows for arbitrary command execution, supporting various Metasploit command payloads. The code is written in Ruby and is structured as a standard Metasploit exploit module.
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.
4 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.