CVE-2012-4412: Buffer Overflow
An integer overflow, leading to buffer overflow flaw was found in the way the implementation of strcoll() routine, used to compare two strings based on the current locale, of glibc, the GNU libc libraries, performed calculation of memory requirements / allocation, needed for storage of the strings. If an application linked against glibc was missing an application-level sanity checks for validity of strcoll() arguments and accepted untrusted input, an attacker could use this flaw to cause the particular application to crash or, potentially, execute arbitrary code with the privileges of the user running the application.
Upstream bug report (including reproducer): [1] http://sourceware.org/bugzilla/showbug.cgi?id=14547
Other sources
Integer overflow in string/strcolll.c in the GNU C Library (aka glibc or libc6) 2.17 and earlier allows context-dependent attackers to cause a denial of service (crash) or possibly execute arbitrary code via a long string, which triggers a heap-based buffer overflow.
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2012-4412?
CVE-2012-4412 has a high severity rating due to the potential for remote code execution through a buffer overflow.
How do I fix CVE-2012-4412?
To fix CVE-2012-4412, upgrade to a version of glibc that is higher than 2.17.
Which versions of glibc are affected by CVE-2012-4412?
CVE-2012-4412 affects glibc versions from 2.0 up to and including 2.17.
What impact does CVE-2012-4412 have on systems?
Systems affected by CVE-2012-4412 may experience a buffer overflow, which can lead to arbitrary code execution.
Is CVE-2012-4412 a local or remote vulnerability?
CVE-2012-4412 is primarily a remote vulnerability that can be exploited over a network.