CVE-2020-1751: High severity GNU glibc vulnerability
An out-of-bounds write vulnerability was found in glibc before 2.31 when handling signal trampolines on PowerPC. Specifically, the backtrace function did not properly check the array bounds when storing the frame address, resulting in a denial of service or potential code execution. The highest threat from this vulnerability is to system availability.
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+deb11u14Fixed in 2.36-9+deb12u14Fixed in 2.36-9+deb12u7Fixed in 2.41-12+deb13u3Fixed in 2.42-17 - Upgrade
Upgrade
glibcto a version that resolves this vulnerability.Fixed in 2.31
Event History
Frequently Asked Questions
What is CVE-2020-1751?
CVE-2020-1751 is an out-of-bounds write vulnerability found in glibc before version 2.31 when handling signal trampolines on PowerPC.
What is the severity of CVE-2020-1751?
CVE-2020-1751 has a severity level of high, with a severity value of 7.
Which software is affected by CVE-2020-1751?
The following software versions are affected: glibc 2.28-10+deb10u1 to 2.28-10+deb10u2, 2.31-13+deb11u6 to 2.31-13+deb11u7, 2.36-9+deb12u2 to 2.36-9+deb12u3, and 2.37-12. Also affected are GNU glibc versions up to 2.31, Redhat Enterprise Linux 8.0, Canonical Ubuntu Linux 16.04, 18.04, and 19.10 with specific versions.
How can I fix CVE-2020-1751 on Debian?
To fix CVE-2020-1751 on Debian, update glibc to versions 2.31-13+deb11u6, 2.31-13+deb11u7, 2.36-9+deb12u2, 2.36-9+deb12u3, or 2.37-12.
How can I fix CVE-2020-1751 on Ubuntu?
To fix CVE-2020-1751 on Ubuntu, update glibc to versions 2.27-3ubuntu1.2 for Ubuntu 16.04 (Xenial), 2.30-0ubuntu2.2 for Ubuntu 18.04 (Bionic), and 2.23-0ubuntu11.2 for Ubuntu 19.10 (Eoan).