Application crash via malformed line-table bounds check
Published Apr 15, 2023 · Updated Feb 6, 2025
Out-of-bounds read in libdwarf before 20201017 allows remote attackers to crash a calling application via a crafted object file. An incorrect bounds test while parsing an invalid .debug_line table permits a pointer dereference one byte beyond the intended section. The application must process the attacker-supplied object; the read can reach unmapped memory and cause a segmentation fault.
Summary
What happened
Out-of-bounds read in libdwarf before 20201017 allows remote attackers to crash a calling application via a crafted object file. An incorrect bounds test while parsing an invalid .debug_line table permits a pointer dereference one byte beyond the intended section. The application must process the attacker-supplied object; the read can reach unmapped memory and cause a segmentation fault.
The record
- CVE
- CVE-2020-27545
- Published
- Apr 15, 2023
- Updated
- Feb 6, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-763, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 15, 2023CVE publishedPublication date reported by the CVE source.
- Feb 6, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- libdwarf regressiontests/c-sun/pocproof of concept · demonstrated
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