Application crash via unchecked DWARF unit length
Published Jun 1, 2022 · Updated Aug 3, 2024
Heap-based buffer over-read in libdwarf 0.4.0 allows local users to crash an application by supplying a corrupted DWARF object file. _dwarf_internal_get_pubnames_like_data trusts a unit length in .debug_pubnames or .debug_pubtypes, letting _dwarf_check_string_valid read beyond the allocated section buffer. The application must process the crafted file; the demonstrated consequence is termination from an invalid read, not confirmed code execution.
Summary
What happened
Heap-based buffer over-read in libdwarf 0.4.0 allows local users to crash an application by supplying a corrupted DWARF object file. _dwarf_internal_get_pubnames_like_data trusts a unit length in .debug_pubnames or .debug_pubtypes, letting _dwarf_check_string_valid read beyond the allocated section buffer. The application must process the crafted file; the demonstrated consequence is termination from an invalid read, not confirmed code execution.
The record
- CVE
- CVE-2022-32200
- Published
- Jun 1, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 1, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
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.
Public exploit references
- Issue 116 crafted-object reproducerproof 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