# CVE-2012-2147: Denial of service in n/a

> Remote attackers can cause denial of service in Munin by sending image requests with large size parameters, consuming disk or memory resources.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Aug 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-2147, GHSA-8h28-5hcj-h4qw

## What is CVE-2012-2147?

CVE-2012-2147 is a medium-severity denial of service vulnerability in n/a, published on 26 Aug 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

munin-cgi-graph in Munin 2.0 rc4 allows remote attackers to cause a denial of service (disk or memory consumption) via many image requests with large values in the (1) size_x or (2) size_y parameters.

Weakness: CWE-399

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

It affects 1 product.


Products: Munin-Monitoring Munin.

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

Upgrade to a fixed version.

## Is CVE-2012-2147 being exploited?

There is no known exploitation of CVE-2012-2147 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-3512](https://insights.sbomify.com/CVE-2012-3512/): Privilege escalation in n/a (high 7.2)
- [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-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-2147 and fix it if it is affected.

What it is: CVE-2012-2147 is a medium-severity denial of service vulnerability in n/a, published on 26 Aug 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-2147 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-2147/ (Markdown: https://insights.sbomify.com/CVE-2012-2147/index.md)
```

## Sources

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

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