libdwarf through 2.3.3 Heap Out-of-Bounds Read via dwarf_debug_addr_table
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fix or patch referenced
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
libdwarf, a library for reading DWARF debugging information in compiled programs, is affected by this flaw, which can let a specially crafted object file cause it to read memory beyond the bounds of a heap buffer. The result can be leakage of nearby heap data or a crash in applications that use the library.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
libdwarf through 2.3.3 contains a heap out-of-bounds read vulnerability in dwarf_debug_addr_table() that omits the table starting offset when validating .debug_addr unit length. Attackers can supply a crafted object file with a non-zero offset table, causing dwarf_debug_addr_by_index() to read past the heap buffer, disclosing adjacent heap bytes or crashing consumers.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- davea42 libdwarf
through 2.3.3