Process crash via stale error-list pointer
Published Mar 18, 2024 · Updated Nov 20, 2025
Double free in Libdwarf Project libdwarf 0.1.0 allows remote attackers to crash a consuming process via a corrupted DWARF object. The unattached Dwarf_Error list retains a pointer after dwarf_dealloc frees the allocation, allowing later list cleanup to free it again. Reachability requires a consuming application to parse a multiply corrupted object that triggers an error before a Dwarf_Debug exists; the demonstrated result is a crash.
Summary
What happened
Double free in Libdwarf Project libdwarf 0.1.0 allows remote attackers to crash a consuming process via a corrupted DWARF object. The unattached Dwarf_Error list retains a pointer after dwarf_dealloc frees the allocation, allowing later list cleanup to free it again. Reachability requires a consuming application to parse a multiply corrupted object that triggers an error before a Dwarf_Debug exists; the demonstrated result is a crash.
The record
- CVE
- CVE-2024-2002
- Published
- Mar 18, 2024
- Updated
- Nov 20, 2025
- Vendor
- Libdwarf Project
- Product
- libdwarf
- Classifications
- CWE-415
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 18, 2024CVE publishedPublication date reported by the CVE source.
- Nov 20, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.1.0
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