# CVE-2012-10048: Zenoss 3.x showDaemonXMLConfig Command Execution

> Authenticated attackers can execute arbitrary commands on Zenoss Core servers via the showDaemonXMLConfig endpoint due to unsanitized input.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Aug 2025
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-r65h-f3rc-mqmw

## What is CVE-2012-10048?

CVE-2012-10048 is a high-severity command injection vulnerability in Zenoss, Inc. Zenoss Core, published on 8 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Zenoss Core 3.x contains a command injection vulnerability in the showDaemonXMLConfig endpoint. The daemon parameter is passed directly to a Popen() call in ZenossInfo.py without proper sanitation, allowing authenticated users to execute arbitrary commands on the server as the zenoss user.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2012-10048?


## How do I fix CVE-2012-10048?

No fix has been published for CVE-2012-10048 yet. Limit exposure of the affected software until one is available.

## Is CVE-2012-10048 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-10048 exists.

Public exploit code:

- Zenoss 3 showDaemonXMLConfig Command Execution (metasploit)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-10048 and fix it if it is affected.

What it is: CVE-2012-10048 is a high-severity command injection vulnerability in Zenoss, Inc. Zenoss Core, published on 8 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-10048 exists.

Affected product: Zenoss, Inc. Zenoss Core. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2012-10048/ (Markdown: https://insights.sbomify.com/CVE-2012-10048/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2012-10048
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-10048
- OSV: https://osv.dev/vulnerability/CVE-2012-10048

---
From sbomify Insights: https://insights.sbomify.com/CVE-2012-10048/
Summaries are generated and may contain mistakes; the official description above is the record.