REDHAT-BUG-681054: Integer Overflow
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] http://scarybeastsecurity.blogspot.com/2011/02/i-got-accidental-code-execution-via.html [2] http://sourceware.org/bugzilla/showbug.cgi?id=11883 [3] http://sourceware.org/git/?p=glibc.git;a=commitdiff;h=f15ce4d8dc139523fe0c273580b604b2453acba6
Affected Software
Event History
Frequently Asked Questions
What is the severity of REDHAT-BUG-681054?
The severity of REDHAT-BUG-681054 is high, as it can lead to application crashes and potentially allow for code execution.
How do I fix REDHAT-BUG-681054?
To fix REDHAT-BUG-681054, update to the patched version of the GNU C Library (glibc) that addresses the vulnerability.
What systems are affected by REDHAT-BUG-681054?
Systems running vulnerable versions of the GNU C Library (glibc) are affected by REDHAT-BUG-681054.
What is the nature of the vulnerability in REDHAT-BUG-681054?
The vulnerability in REDHAT-BUG-681054 is caused by improper handling of user-supplied UTF8 strings leading to stack overflow.
Is there a known exploit for REDHAT-BUG-681054?
As of now, there are no public exploits specifically targeting REDHAT-BUG-681054, but the nature of the vulnerability may encourage future exploit development.