CWE
399 190
Advisory Published
CVE Published
Updated

CVE-2011-1071: Integer Overflow

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 SoftwareAffected VersionHow 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

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2011-1071?

    CVE-2011-1071 has a severity rating of medium due to its potential to cause application crashes.

  • How do I fix CVE-2011-1071?

    To fix CVE-2011-1071, upgrade to a version of glibc that is not affected, specifically versions later than 2.12.1.

  • What are the affected versions for CVE-2011-1071?

    CVE-2011-1071 affects multiple versions of GNU C Library (glibc) including 2.2, 2.3, and up to 2.12.1.

  • Can CVE-2011-1071 be exploited remotely?

    CVE-2011-1071 is not typically exploited remotely as it generally requires user-supplied input.

  • What is the impact of CVE-2011-1071 on applications?

    CVE-2011-1071 can lead to application crashes due to stack overflow caused by improper handling of user-supplied UTF8 strings.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203