Integer overflow in GNU Glibc

CVE-2020-6096

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.

EPSS: 0.054 (92.1th percentile) — read the EPSS interpretation.

CVSS v3 metric

CVSS v3 base score 8.1 (High). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.

Affected products

Weakness classification (CWE)

Public proof-of-concept exploits

References

Frequently asked questions

What is CVE-2020-6096?
CVE-2020-6096 is a high-severity vulnerability in GNU Glibc, classified under CWE-195. CVSS score: 8.1/10. Published 2020-04-01.
How severe is CVE-2020-6096?
High severity. CVSS v3 base score is 8.1 out of 10.
Is CVE-2020-6096 known to be exploited?
25 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.