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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
davea42 libdwarf
Default version status: unaffected
0 to ≤ 2.3.3affected
pkg:github/davea42/libdwarf-codeReferences
- https://github.com/davea42/libdwarf-code/issues/336 ↗
- https://github.com/davea42/libdwarf-code ↗
- https://github.com/davea42/libdwarf-code/commit/71f04013ddc2a3c88b9e25a4162ee2824741b593 ↗
- https://github.com/davea42/libdwarf-code/blob/v2.3.3/src/lib/libdwarf/dwarf_debugaddr.c#L175-L216 ↗
- https://hackmd.io/@haindpwn/libdwarf-debug-addr-table-section-offset-oob-read ↗
- https://www.vulncheck.com/advisories/libdwarf-through-2.3.3-heap-out-of-bounds-read-via-dwarf-debug-addr-table ↗