# CVE-2012-3512: Privilege escalation in n/a

> Local attackers can escalate privileges to root by replacing group-writable state files in Munin's plugin directory.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Nov 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-3512, GHSA-g93j-j4g4-hr9q

## What is CVE-2012-3512?

CVE-2012-3512 is a high-severity vulnerability in n/a, published on 21 Nov 2012. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Munin before 2.0.6 stores plugin state files that run as root in the same group-writable directory as non-root plugins, which allows local users to execute arbitrary code by replacing a state file, as demonstrated using the smart_ plugin.

Weakness: CWE-264

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

It affects 1 product.


Products: Munin-Monitoring Munin.

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

Upgrade to a fixed version.

## Is CVE-2012-3512 being exploited?

There is no known exploitation of CVE-2012-3512 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2012-3513](https://insights.sbomify.com/CVE-2012-3513/): Missing authorization in n/a (critical 9.3)
- [CVE-2012-2104](https://insights.sbomify.com/CVE-2012-2104/): Command injection in n/a (medium 6.8)
- [CVE-2013-6048](https://insights.sbomify.com/CVE-2013-6048/): Denial of service in n/a (medium 5.0)
- [CVE-2012-2147](https://insights.sbomify.com/CVE-2012-2147/): Denial of service in n/a (medium 5.0)
- [CVE-2012-4678](https://insights.sbomify.com/CVE-2012-4678/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-3512 is a high-severity vulnerability in n/a, published on 21 Nov 2012. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-3512 in the wild and no public exploit code.

Affected product: n/a. 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-3512/ (Markdown: https://insights.sbomify.com/CVE-2012-3512/index.md)
```

## Sources

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

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