First published: Mon Feb 28 2011(Updated: )
It was reported [1] that glibc had a bug where it would use alloca() for the length of a user-supplied UTF8 string, times four (with additional integer overflow in the times four). This could lead to an application crash, because alloca() extends the stack. This was reported upstream [2] and subsequently fixed upstream [3]. References: [1] <a href="http://scarybeastsecurity.blogspot.com/2011/02/i-got-accidental-code-execution-via.html">http://scarybeastsecurity.blogspot.com/2011/02/i-got-accidental-code-execution-via.html</a> [2] <a href="http://sourceware.org/bugzilla/show_bug.cgi?id=11883">http://sourceware.org/bugzilla/show_bug.cgi?id=11883</a> [3] <a href="http://sourceware.org/git/?p=glibc.git;a=commitdiff;h=f15ce4d8dc139523fe0c273580b604b2453acba6">http://sourceware.org/git/?p=glibc.git;a=commitdiff;h=f15ce4d8dc139523fe0c273580b604b2453acba6</a>
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
GNU C Library (glibc) | =2.2.2 | |
GNU C Library (glibc) | =2.9 | |
GNU C Library (glibc) | =2.7 | |
GNU C Library (glibc) | =2.1.2 | |
GNU C Library (glibc) | =2.11 | |
GNU C Library (glibc) | =2.0.5 | |
GNU C Library (glibc) | =2.2.5 | |
GNU C Library (glibc) | =2.0.6 | |
GNU C Library (glibc) | =2.10.1 | |
GNU C Library (glibc) | =1.00 | |
GNU C Library (glibc) | =1.06 | |
GNU C Library (glibc) | =2.1.1 | |
GNU C Library (glibc) | =1.02 | |
GNU C Library (glibc) | =2.0.3 | |
GNU C Library (glibc) | =1.07 | |
GNU C Library (glibc) | =2.3.1 | |
GNU C Library (glibc) | =2.3 | |
GNU C Library (glibc) | =2.12.0 | |
GNU C Library (glibc) | =2.0 | |
GNU C Library (glibc) | =2.1.1.6 | |
GNU C Library (glibc) | =1.04 | |
GNU C Library (glibc) | =1.01 | |
GNU C Library (glibc) | =2.3.10 | |
GNU C Library (glibc) | =2.4 | |
GNU C Library (glibc) | =2.1 | |
GNU C Library (glibc) | =2.3.4 | |
GNU C Library (glibc) | =1.09.1 | |
GNU C Library (glibc) | =2.1.9 | |
GNU C Library (glibc) | <=2.12.1 | |
GNU C Library (glibc) | =2.3.3 | |
GNU C Library (glibc) | =2.6.1 | |
GNU C Library (glibc) | =2.0.1 | |
GNU C Library (glibc) | =1.09 | |
GNU C Library (glibc) | =2.10 | |
GNU C Library (glibc) | =2.11.2 | |
GNU C Library (glibc) | =2.5.1 | |
GNU C Library (glibc) | =2.6 | |
GNU C Library (glibc) | =2.0.4 | |
GNU C Library (glibc) | =2.0.2 | |
GNU C Library (glibc) | =2.2.1 | |
GNU C Library (glibc) | =2.3.2 | |
GNU C Library (glibc) | =1.03 | |
GNU C Library (glibc) | =2.1.3.10 | |
GNU C Library (glibc) | =2.3.6 | |
GNU C Library (glibc) | =2.2.3 | |
GNU C Library (glibc) | =2.5 | |
GNU EGLIBC | ||
GNU C Library (glibc) | =2.11.3 | |
GNU C Library (glibc) | =1.08 | |
GNU C Library (glibc) | =2.3.5 | |
GNU C Library (glibc) | =2.8 | |
GNU C Library (glibc) | =2.11.1 | |
GNU C Library (glibc) | =2.2.4 | |
GNU C Library (glibc) | =2.1.3 | |
GNU C Library (glibc) | =1.05 | |
GNU C Library (glibc) | =2.2 | |
GNU C Library (glibc) | =2.10.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2011-1071 has a severity rating of medium due to its potential to cause application crashes.
To fix CVE-2011-1071, upgrade to a version of glibc that is not affected, specifically versions later than 2.12.1.
CVE-2011-1071 affects multiple versions of GNU C Library (glibc) including 2.2, 2.3, and up to 2.12.1.
CVE-2011-1071 is not typically exploited remotely as it generally requires user-supplied input.
CVE-2011-1071 can lead to application crashes due to stack overflow caused by improper handling of user-supplied UTF8 strings.