# CVE-2012-6096: Memory corruption in n/a

> Remote attackers can execute arbitrary code via stack-based buffer overflows in Nagios Core and Icinga history.cgi parameters.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Jan 2013
- **Updated:** 6 Aug 2024
- **Also known as:** DSA-2616-1, DSA-2653-1, GHSA-976m-29vc-cxx7

## What is CVE-2012-6096?

CVE-2012-6096 is a high-severity memory corruption vulnerability in n/a, published on 22 Jan 2013. It can be exploited over the network, with no action from the victim.

### Official description

Multiple stack-based buffer overflows in the get_history function in history.cgi in Nagios Core before 3.4.4, and Icinga 1.6.x before 1.6.2, 1.7.x before 1.7.4, and 1.8.x before 1.8.4, might allow remote attackers to execute arbitrary code via a long (1) host_name variable (host parameter) or (2) svc_description variable.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 2 products.


Products: Icinga Icinga, Nagios Nagios.

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

Upgrade to a fixed version.

## Is CVE-2012-6096 being exploited?

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

Public exploit code:

- Nagios3 history.cgi Host Command Execution (metasploit)
- Nagios3 - 'history.cgi' Remote Command Execution (exploitdb)
- Nagios3 - 'history.cgi' Host Command Execution (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2025-48057](https://insights.sbomify.com/CVE-2025-48057/): Icinga 2 certificate renewal might incorrectly renew an invalid certificate (critical 9.3)
- [CVE-2020-29663](https://insights.sbomify.com/CVE-2020-29663/): Security feature bypass in n/a (critical 9.1)
- [CVE-2024-24820](https://insights.sbomify.com/CVE-2024-24820/): Icinga Director configuration is susceptible to Cross-Site Request Forgery (high 8.3)
- [CVE-2018-6535](https://insights.sbomify.com/CVE-2018-6535/): Information disclosure in n/a (high 8.1)
- [CVE-2020-14004](https://insights.sbomify.com/CVE-2020-14004/): Path traversal in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-6096 is a high-severity memory corruption vulnerability in n/a, published on 22 Jan 2013. It can be exploited 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-6096 exists.

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-6096/ (Markdown: https://insights.sbomify.com/CVE-2012-6096/index.md)
```

## Sources

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

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