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>
Affected Software | Affected Version | How to fix |
---|---|---|
GNU C Library (glibc) |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-681054 is high, as it can lead to application crashes and potentially allow for code execution.
To fix REDHAT-BUG-681054, update to the patched version of the GNU C Library (glibc) that addresses the vulnerability.
Systems running vulnerable versions of the GNU C Library (glibc) are affected by REDHAT-BUG-681054.
The vulnerability in REDHAT-BUG-681054 is caused by improper handling of user-supplied UTF8 strings leading to stack overflow.
As of now, there are no public exploits specifically targeting REDHAT-BUG-681054, but the nature of the vulnerability may encourage future exploit development.