CVE-2022-34299 json
There is a heap-based buffer over-read in libdwarf 0.4.0.
published 2022-06-22 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-37256
- cvss
- 8.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 73%
- public exploits
- 0
- none known
Summary
There is a heap-based buffer over-read in libdwarf 0.4.0. This issue is related to dwarf_global_formref_b.
Patch / fix
- dwarfutils Debian 14, Debian 13 1:0.11.1-1
debian advisories DEBIAN-CVE-2022-34299
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-34299 updated cvss 7.1
libdwarf: heap buffer over-read in dwarf_global_formref_b() in dwarf_form.c
-
Red Hat Enterprise Linux 7 libdwarf, libdwarf-tools Red Hat Enterprise Linux 8 libdwarf, libdwarf-toolsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.43% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/davea42/libdwarf-code/issues/119 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H |
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:P/I:N/A:P |
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
References
-
github.com
/davea42/libdwarf-code/commit/7ef09e1fc9ba07653dd078edb2408631c7969162
patch, third-party-advisory
-
github.com
/davea42/libdwarf-code/issues/119
exploit, issue-tracking, third-party-advisory
Sources
- CVE List CVE-2022-34299
- NVD CVE-2022-34299
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.