CVE-2012-4424: Buffer Overflow
A security flaw was found in the way strcoll() interface of glibc, the GNU libc libraries, performed failsafe back to alloca() routine when malloc() function call failed previously (due to out of memory [OOM] condition for example). 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 the reproducer): [1] http://sourceware.org/bugzilla/showbug.cgi?id=14552#c0
Issue / part: 1) alloca() stack overflow from [1].
References: [2] http://www.openwall.com/lists/oss-security/2012/09/07/9 [3] http://www.openwall.com/lists/oss-security/2012/09/07/15 [4] http://www.openwall.com/lists/oss-security/2012/09/10/1 [5] http://www.openwall.com/lists/oss-security/2012/09/10/3 [6] http://www.openwall.com/lists/oss-security/2012/09/13/16
Other sources
Stack-based buffer 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 that triggers a malloc failure and use of the alloca function.
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2012-4424?
CVE-2012-4424 is classified as a medium severity vulnerability.
How do I fix CVE-2012-4424?
To fix CVE-2012-4424, update the GNU C Library (glibc) to version 2.18 or later.
What causes the CVE-2012-4424 vulnerability?
CVE-2012-4424 is caused by a flaw in the strcoll() function of glibc when handling memory allocation failures.
Which versions of glibc are affected by CVE-2012-4424?
CVE-2012-4424 affects glibc versions prior to 2.18, including all versions up to and including 2.17.
What impact does CVE-2012-4424 have on affected systems?
CVE-2012-4424 may lead to unexpected behavior or crashes in applications linked against the vulnerable version of glibc.