CVE-2020-6096
Last modified
CVE-2020-6096 is a high-severity vulnerability rated 8.1/10 on the CVSS scale. 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. EPSS estimates a 5.22% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Gnu | Glibc | <= 2.31 |
| Fedoraproject | Fedora | 31 |
| Fedoraproject | Fedora | 32 |
| Debian | Debian Linux | 10.0 |
References
- https://lists.debian.org/debian-lts-announce/2022/10/msg00021.htmlMailing List, Third Party Advisory
- https://security.gentoo.org/glsa/202101-20Third Party Advisory
- https://sourceware.org/bugzilla/show_bug.cgi?id=25620Issue Tracking, Third Party Advisory
- https://www.talosintelligence.com/vulnerability_reports/TALOS-2020-1019Third Party Advisory
- https://lists.debian.org/debian-lts-announce/2022/10/msg00021.htmlMailing List, Third Party Advisory
- https://security.gentoo.org/glsa/202101-20Third Party Advisory
- https://sourceware.org/bugzilla/show_bug.cgi?id=25620Issue Tracking, Third Party Advisory
- https://www.talosintelligence.com/vulnerability_reports/TALOS-2020-1019Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2020-6096?
How severe is CVE-2020-6096?
How do I fix CVE-2020-6096?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2020
- CVE-2020-6090An exploitable code execution vulnerability exists in the We…7.2
- CVE-2020-6091An exploitable authentication bypass vulnerability exists in…9.1
- CVE-2020-6092An exploitable code execution vulnerability exists in the wa…7.8
- CVE-2020-6093An exploitable information disclosure vulnerability exists i…5.5
- CVE-2020-6094An exploitable code execution vulnerability exists in the TI…8.8
- CVE-2020-6095An exploitable denial of service vulnerability exists in the…7.5
- CVE-2020-6097An exploitable denial of service vulnerability exists in the…7.5
- CVE-2020-6098An exploitable denial of service vulnerability exists in the…7.5
- CVE-2020-6099An exploitable code execution vulnerability exists in the fi…7.8
- CVE-2020-6100An exploitable memory corruption vulnerability exists in AMD…9.9
- CVE-2020-6101An exploitable code execution vulnerability exists in the Sh…9.9
- CVE-2020-6102An exploitable code execution vulnerability exists in the Sh…9.9
Are you affected by CVE-2020-6096?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
