Application crash via stale frame-instruction pointer
Published Sep 2, 2022 · Updated Aug 3, 2024
Double free in libdwarf 0.4.1 allows context-dependent attackers to crash a calling application via a crafted object file. _dwarf_exec_frame_instr retains a stale dfi pointer after linking it into the instruction list, so error cleanup frees the same allocation twice. The application must process attacker-controlled corrupt frame data, and the documented consequence is process termination rather than code execution.
Summary
What happened
Double free in libdwarf 0.4.1 allows context-dependent attackers to crash a calling application via a crafted object file. _dwarf_exec_frame_instr retains a stale dfi pointer after linking it into the instruction list, so error cleanup frees the same allocation twice. The application must process attacker-controlled corrupt frame data, and the documented consequence is process termination rather than code execution.
The record
- CVE
- CVE-2022-39170
- Published
- Sep 2, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-415, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 2, 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.
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.
Public exploit references
- Crafted DWARF object proof of conceptproof 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