libdwarf vulnerabilities

The dwarf_macro5.c file in libdwarf before version 20160923 contains a vulnerability that allows remote attackers to cause a denial of service (NULL pointer dereference) via a debugging information entry using DWARF5 without a DW_AT_name.

The dwarf_get_aranges_list function in dwarf_arrange.c in Libdwarf before version 20161124 allows remote attackers to cause a denial of service via an out-of-bounds read.

Heap-based buffer overflow in the _dwarf_skim_forms function in libdwarf/dwarf_macro5.c in Libdwarf before version 20161124 can be exploited by remote attackers.

The WRITE_UNALIGNED function in dwarf_elf_access.c in libdwarf before version 20160923 allows remote attackers to cause a denial of service (out-of-bounds write and crash) via a crafted DWARF section.

The dwarf_dealloc function in libdwarf before version 20160923 allows remote attackers to cause a denial of service (out-of-bounds read and crash) via a crafted DWARF section.

The dwarf_get_aranges_list function in libdwarf before version 20160923 allows remote attackers to cause a denial of service (infinite loop and crash) via a crafted DWARF section.

libdwarf before version 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.

The get_attr_value function in libdwarf before 20160923 allows remote attackers to cause a denial of service (out-of-bounds read) via a crafted object with all-bits on.

The dwarf_get_macro_startend_file function in libdwarf before version 20160923 allows remote attackers to cause a denial of service (out-of-bounds read) via a crafted string offset for .debug_str.

The dump_block function in print_sections.c in libdwarf before version 20160923 allows remote attackers to cause a denial of service (out-of-bounds read) via crafted frame data.

An issue, also known as DW201703-001, was discovered in libdwarf in the function dwarf_formsdata(). A few data types were not checked for being in bounds, leading to a heap-based buffer over-read.

An issue was discovered in the libdwarf library that leads to a heap-based buffer over-read. The problem occurs in the _dwarf_decode_s_leb128_chk() function, where a byte pointer is dereferenced before being checked for bounds.

An issue was discovered in libdwarf related to a heap-based buffer over-read in the _dwarf_read_loc_expr_op() function. This problem is due to a failure to check if a pointer is within bounds.

An issue was discovered in the libdwarf library related to a heap-based buffer over-read in the dwarf_formsdata() function. This problem arises from a failure to check if a pointer is in bounds in several places in this function and a failure in a check in the dwarf_attr_list() function.

In libdwarf before version 20161124, there is a vulnerability that allows remote attackers to have unspecified impact via a crafted bit pattern in a signed leb number, known as a 'negation overflow'.

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.