CVE-2012-10048 is a command injection vulnerability in Zenoss Core 3.x affecting the showDaemonXMLConfig endpoint. The issue is caused by the daemon parameter being passed directly to a Python Popen() call in ZenossInfo.py without proper sanitization or neutralization of shell metacharacters. An authenticated user can supply crafted input in the daemon parameter to inject and execute arbitrary operating system commands on the underlying server in the security context of the zenoss user.
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 targeting a command execution vulnerability in Zenoss 3.x (CVE-2012-10048). The exploit abuses the 'showDaemonXMLConfig' endpoint, which is accessible to authenticated users, to execute arbitrary commands as the 'zenoss' user. The module requires valid Zenoss credentials and interacts with the application over HTTP, typically on port 8080. The payload is customizable and delivered via a POST request to '/zport/About/showDaemonXMLConfig', with the command injected into the 'daemon' parameter. The module also includes a check method to verify the target's version and authentication status. The code is written in Ruby and 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.
3 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.