CVE-2020-6096: Integer Underflow
An exploitable signed comparison vulnerability exists in the ARMv7 memcpy() implementation of GNU glibc 2.30.9000. Calling memcpy() (on ARMv7 targets that utilize the GNU glibc implementation) with a negative value for the 'num' parameter results in a signed comparison vulnerability. If an attacker underflows the 'num' parameter to memcpy(), this vulnerability could lead to undefined behavior such as writing to out-of-bounds memory and potentially remote code execution. Furthermore, this memcpy() implementation allows for program execution to continue in scenarios where a segmentation fault or crash should have occurred. The dangers occur in that subsequent execution and iterations of this code will be executed with this corrupted data.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/glibcto a version that resolves this vulnerability.Fixed in 2.31-13+deb11u11Fixed in 2.31-13+deb11u10Fixed in 2.36-9+deb12u10Fixed in 2.36-9+deb12u7Fixed in 2.41-7
Event History
Frequently Asked Questions
What is the vulnerability ID for this issue?
The vulnerability ID for this issue is CVE-2020-6096.
What is the severity level of CVE-2020-6096?
The severity level of CVE-2020-6096 is high with a score of 8.1.
Which software is affected by CVE-2020-6096?
The GNU glibc versions up to and including 2.31, Fedora versions 31 and 32, and Debian Linux version 10.0 are affected by CVE-2020-6096.
What is the description of CVE-2020-6096?
CVE-2020-6096 is an exploitable signed comparison vulnerability in the ARMv7 memcpy() implementation of GNU glibc 2.30.9000.
How can CVE-2020-6096 be exploited?
CVE-2020-6096 can be exploited by calling memcpy() with a negative value for the 'num' parameter in ARMv7 targets that utilize the GNU glibc implementation.