CVE-2020-6096 is a signed comparison vulnerability in the ARMv7 memcpy() implementation of GNU glibc 2.30.9000, affecting various Debian, Fedora, and GNU glibc distributions. By providing a negative 'num' parameter, an attacker can trigger undefined behavior, potentially leading to out-of-bounds memory writes and remote code execution. This vulnerability has a CVSS score of 8.1 (High), indicating a network-based attack with high impact on confidentiality, integrity, and availability, but requires high attack complexity. There is currently no evidence of active exploitation, public exploit code (Metasploit, Nuclei, ExploitDB), or significant community discussion surrounding this CVE.
| Vendor | Product | Version(s) | CPE |
|---|---|---|---|
<= 2.31CPE matchmatch criteria | cpe:2.3:a:gnu:glibc:*:*:*:*:*:*:*:* | ||
31CPE matchmatch criteria | cpe:2.3:o:fedoraproject:fedora:31:*:*:*:*:*:*:* | ||
32CPE matchmatch criteria | cpe:2.3:o:fedoraproject:fedora:32:*:*:*:*:*:*:* | ||
10.0CPE matchmatch criteria | cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:* |
CVSS version used by this source: 3.0
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
The average CVE in this peer group has 0.0 Twitter, 0.1 Reddit, 0.1 Bluesky, 0.0 Mastodon, and 0.2 GitHub mentions.
No media coverage found for this CVE.
The average CVE in this peer group has 0.1 InfoSec Media, 0.0 Vendor Blog, and 0.0 Security Researcher mentions.
Multiple ctrlX CORE vulnerabilities
Apr 20, 2022Multiple ctrlX CORE vulnerabilities
Apr 20, 2022Multiple ctrlX CORE vulnerabilities
Apr 20, 2022Multiple ctrlX CORE vulnerabilities
Apr 20, 2022Multiple ctrlX CORE vulnerabilities
Apr 20, 2022Multiple ctrlX CORE vulnerabilities
Apr 20, 2022CVE-2020-6096
Sep 8, 2020An 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.
Apr 14, 2020glibc: signed comparison vulnerability in the ARMv7 memcpy function
Mar 2, 2020