CVE-2012-6096: Buffer Overflow
It was reported [1] that Nagios Core's history.cgi is vulnerable to a buffer overflow because it used sprintf on user-supplied data that was not restricted in size.
Due to various protections of the operating system (history.cgi is compiled with SSP, FORTIFYSOURCE is enabled, etc.) this is not believed to be exploitable and would result in a denial of service to the user sending the input to history.cgi.
This has been fixed in svn (r2547)[2].
[1] http://archives.neohapsis.com/archives/fulldisclosure/2012-12/0108.html [2] http://nagios.svn.sourceforge.net/viewvc/nagios?view=revision&revision=2547
Other sources
Multiple stack-based buffer overflows in the gethistory 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) hostname variable (host parameter) or (2) svcdescription variable.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2012-6096?
CVE-2012-6096 is classified as a medium severity vulnerability due to its potential for causing buffer overflows.
How do I fix CVE-2012-6096?
To mitigate CVE-2012-6096, update Nagios Core to version 3.4.4 or higher, as these versions contain the necessary security patches.
Which versions of Nagios are affected by CVE-2012-6096?
CVE-2012-6096 affects Nagios Core versions up to and including 3.4.3 and various earlier versions.
Can CVE-2012-6096 lead to remote code execution?
Yes, CVE-2012-6096 could potentially allow an attacker to execute arbitrary code via a crafted request due to the buffer overflow.
Is CVE-2012-6096 still a risk if my system has security features enabled?
Despite some protections like SSP and FORTIFY_SOURCE, CVE-2012-6096 can still be exploited, making it important to apply the fix.