Process crash via PowerPC backtrace array overflow
Published Apr 17, 2020 · Updated Aug 4, 2024
Out-of-bounds writes in glibc before 2.31 allow local users on PowerPC systems to crash a process during signal-frame unwinding. PowerPC 32-bit and 64-bit __backtrace increment the frame count and store a recovered instruction address without first ensuring that another array slot exists. Reachability requires unwinding through a signal trampoline; availability loss is the primary threat, and the record identifies code execution as a potential consequence.
Summary
What happened
Out-of-bounds writes in glibc before 2.31 allow local users on PowerPC systems to crash a process during signal-frame unwinding. PowerPC 32-bit and 64-bit __backtrace increment the frame count and store a recovered instruction address without first ensuring that another array slot exists. Reachability requires unwinding through a signal trampoline; availability loss is the primary threat, and the record identifies code execution as a potential consequence.
The record
- CVE
- CVE-2020-1751
- Published
- Apr 17, 2020
- Updated
- Aug 4, 2024
- Vendor
- Red Hat
- Product
- GNU C Library (glibc)
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 17, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.31
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo