CVE-2012-6096 Memory corruption in n/a

High 7.5 Published Updated

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

Exploited in the wild
Not known
Login needed
Not stated
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

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

Which versions are affected by CVE-2012-6096?

It affects 2 products.

Products include Icinga Icinga, Nagios Nagios.

How do I fix CVE-2012-6096?

Upgrade to a fixed version.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

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: 1 Metasploit module and 2 Exploit-DB entries.

Sources

Also known as DSA-2616-1, DSA-2653-1, GHSA-976m-29vc-cxx7.

Is CVE-2012-6096 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free