Libdwarf is a debugging-information library embedded across compiler toolchains, debuggers, and binary-analysis tools, where its role in parsing DWARF debug symbols positions it as a deep dependency in the development and analysis ecosystem. Despite its narrow product scope, the library's prevalence in widely deployed tooling elevates its significance in the vulnerability landscape. Vulnerabilities affecting Libdwarf skew toward serious outcomes, with a meaningful share reaching critical severity, and concentrate in memory-safety weakness classes including out-of-bounds reads and writes, NULL-pointer dereferences, double-free conditions, and buffer-boundary violations that are characteristic of C-based parsing libraries handling untrusted debug data. Defenders should track Libdwarf updates closely and prioritize rebuilds of downstream tools and compiler infrastructure, since a single library fix may require propagation across a broad set of dependent products. Current exploitation activity and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Libdwarf Project over time
Signals from CVEs in this vendor scope (45 CVEs).
45 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2016-9558CRITICAL (1) libdwarf/dwarf_leb.c and (2) dwarfdump/print_frames.c in libdwarf before 20161124 allow remote attackers to have unspecified impact via a crafted bit pattern in a signed leb nu | Feb 28, 2017 | 9.8 | 33 | NO | NO |
CVE-2017-9054CRITICAL An issue, also known as DW201703-002, was discovered in libdwarf 2017-03-21. In _dwarf_decode_s_leb128_chk() a byte pointer was dereferenced just before it was checked for being in | May 18, 2017 | 9.8 | 31 | NO | NO |
CVE-2017-9055CRITICAL An issue, also known as DW201703-001, was discovered in libdwarf 2017-03-21. In dwarf_formsdata() a few data types were not checked for being in bounds, leading to a heap-based buf | May 18, 2017 | 9.8 | 30 | NO | NO |
CVE-2017-9052CRITICAL An issue, also known as DW201703-006, was discovered in libdwarf 2017-03-21. A heap-based buffer over-read in dwarf_formsdata() is due to a failure to check a pointer for being in | May 18, 2017 | 9.8 | 30 | NO | NO |
CVE-2022-39170HIGH libdwarf 0.4.1 has a double free in _dwarf_exec_frame_instr in dwarf_frame.c. | Sep 2, 2022 | 8.8 | 28 | NO | NO |
CVE-2017-9053CRITICAL An issue, also known as DW201703-005, was discovered in libdwarf 2017-03-21. A heap-based buffer over-read in _dwarf_read_loc_expr_op() is due to a failure to check a pointer for b | May 18, 2017 | 9.1 | 28 | NO | NO |
CVE-2016-5040HIGH libdwarf before 20160923 allows remote attackers to cause a denial of service (out-of-bounds read and crash) via a large length value in a compilation unit header. | Feb 17, 2017 | 7.5 | 26 | NO | NO |
CVE-2024-2002HIGH A double-free vulnerability was found in libdwarf. In a multiply-corrupted DWARF object, libdwarf may try to dealloc(free) an allocation twice, potentially causing unpredictable an | Mar 18, 2024 | 7.5 | 25 | NO | NO |
CVE-2022-34299HIGH There is a heap-based buffer over-read in libdwarf 0.4.0. This issue is related to dwarf_global_formref_b. | Jun 23, 2022 | 8.1 | 25 | NO | NO |
CVE-2016-5041HIGH dwarf_macro5.c in libdwarf before 20160923 allows remote attackers to cause a denial of service (NULL pointer dereference) via a debugging information entry using DWARF5 and withou | Apr 10, 2017 | 7.5 | 25 | NO | NO |
Signals from CVEs in this vendor scope (45 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Libdwarf Project.
Media articles that mention a CVE ID that affects a product developed by Libdwarf Project — matched by CVE ID, not by vendor name.