This update for binutils to 2.31 fixes the following issues: These security issues were fixed: - CVE-2017-15996: readelf allowed remote attackers to cause a denial of service or possibly have unspecified other impact via a crafted ELF file that triggered a buffer overflow on fuzzed archive header . - CVE-2017-15939: Binary File Descriptor library mishandled NULL files in a .debug_line file table, which allowed remote attackers to cause a denial of service via a crafted ELF file, related to concat_filename . - CVE-2017-15938: the Binary File Descriptor library miscalculated DW_FORM_ref_addr die refs in the case of a relocatable object file, which allowed remote attackers to cause a denial of service . - CVE-2017-16826: The coff_slurp_line_table function the Binary File Descriptor library allowed remote attackers to cause a denial of service or possibly have unspecified other impact via a crafted PE file . - CVE-2017-16832: The pe_bfd_read_buildid function in the Binary File Descriptor library did not validate size and offset values in the data dictionary, which allowed remote attackers to cause a denial of service or possibly have unspecified other impact via a crafted PE file . - CVE-2017-16831: Binary File Descriptor library did not validate the symbol count, which allowed remote attackers to cause a denial of service or possibly have unspecified other impact via a crafted PE file . - CVE-2017-16830: The print_gnu_property_note function did not have integer-overflow protection on 32-bit platforms, which allowed remote attackers to cause a denial of service or possibly have unspecified other impact via a crafted ELF file . - CVE-2017-16829: The _bfd_elf_parse_gnu_properties function in the Binary File Descriptor library did not prevent negative pointers, which allowed remote attackers to cause a denial of service or possibly have unspecified other impact via a crafted ELF file . - CVE-2017-16828: The display_debug_frames function allowed remote attackers to cause a denial of service or possibly have unspecified other impact via a crafted ELF file . - CVE-2017-16827: The aout_get_external_symbols function in the Binary File Descriptor library allowed remote attackers to cause a denial of service or possibly have unspecified other impact via a crafted ELF file . - CVE-2018-6323: The elf_object_p function in the Binary File Descriptor library had an unsigned integer overflow because bfd_size_type multiplication is not used. A crafted ELF file allowed remote attackers to cause a denial of service or possibly have unspecified other impact . - CVE-2018-6543: Prevent integer overflow in the function load_specific_debug_section which resulted in `malloc` with 0 size. A crafted ELF file allowed remote attackers to cause a denial of service or possibly have unspecified other impact . - CVE-2018-6759: The bfd_get_debug_link_info_1 function in the Binary File Descriptor library had an unchecked strnlen operation. Remote attackers could have leveraged this vulnerability to cause a denial of service via a crafted ELF file . - CVE-2018-6872: The elf_parse_notes function in the Binary File Descriptor library allowed remote attackers to cause a denial of service via a note with a large alignment . - CVE-2018-7208: In the coff_pointerize_aux function in the Binary File Descriptor library an index was not validated, which allowed remote attackers to cause a denial of service or possibly have unspecified other impact via a crafted file, as demonstrated by objcopy of a COFF object . - CVE-2018-7570: The assign_file_positions_for_non_load_sections function in the Binary File Descriptor library allowed remote attackers to cause a denial of service via an ELF file with a RELRO segment that lacks a matching LOAD segment, as demonstrated by objcopy . - CVE-2018-7569: The Binary File Descriptor library allowed remote attackers to cause a denial of service via an ELF file with a corrupt DWARF FORM block, as demonstrated by nm . - CVE-2018-8945: The bfd_section_from_shdr function in the Binary File Descriptor library allowed remote attackers to cause a denial of service via a large attribute section . - CVE-2018-7643: The display_debug_ranges function allowed remote attackers to cause a denial of service or possibly have unspecified other impact via a crafted ELF file, as demonstrated by objdump . - CVE-2018-7642: The swap_std_reloc_in function in the Binary File Descriptor library allowed remote attackers to cause a denial of service via a crafted ELF file, as demonstrated by objcopy . - CVE-2018-7568: The parse_die function in the Binary File Descriptor library allowed remote attackers to cause a denial of service via an ELF file with corrupt dwarf1 debug information, as demonstrated by nm . - CVE-2018-10373: concat_filename in the Binary File Descriptor library allowed remote attackers to cause a denial of service via a crafted binary file, as demonstrated by nm-new . - CVE-2018-10372: process_cu_tu_index allowed remote attackers to cause a denial of service via a crafted binary file, as demonstrated by readelf . - CVE-2018-10535: The ignore_section_sym function in the Binary File Descriptor library did not validate the output_section pointer in the case of a symtab entry with a quot;SECTIONquot; type that has a quot;0quot; value, which allowed remote attackers to cause a denial of service via a crafted file, as demonstrated by objcopy . - CVE-2018-10534: The _bfd_XX_bfd_copy_private_bfd_data_common function in the Binary File Descriptor library processesed a negative Data Directory size with an unbounded loop that increased the value of *edd so that the address exceeded its own memory region, resulting in an out-of-bounds memory write, as demonstrated by objcopy copying private info with _bfd_pex64_bfd_copy_private_bfd_data_common in pex64igen.c . These non-security issues were fixed: - The AArch64 port now supports showing disassembly notes which are emitted when inconsistencies are found with the instruction that may result in the instruction being invalid. These can be turned on with the option -M notes to objdump. - The AArch64 port now emits warnings when a combination of an instruction and a named register could be invalid. - Added O modifier to ar to display member offsets inside an archive - The ADR and ADRL pseudo-instructions supported by the ARM assembler now only set the bottom bit of the address of thumb function symbols if the -mthumb-interwork command line option is active. - Add --generate-missing-build-notes=[yes|no] option to create GNU Build Attribute notes if none are present in the input sources. Add a --enable-generate-build-notes=[yes|no] configure time option to set the default behaviour. Set the default if the configure option is not used to quot;noquot;. - Remove -mold-gcc command-line option for x86 targets. - Add -O[2|s] command-line options to x86 assembler to enable alternate shorter instruction encoding. - Add support for .nops directive. It is currently supported only for x86 targets. - Speed up direct linking with DLLs for Cygwin and Mingw targets. - Add a configure option --enable-separate-code to decide whether -z separate-code should be enabled in ELF linker by default. Default to yes for Linux/x86 targets. Note that -z separate-code can increase disk and memory size. - RISC-V: Fix symbol address problem with versioned symbols - Restore riscv64-elf cross prefix via symlinks - RISC-V: Don"t enable relaxation in relocatable link - Prevent linking faiures on i386 with assertion - Fix symbol size bug when relaxation deletes bytes - Add --debug-dump=links option to readelf and --dwarf=links option to objdump which displays the contents of any .gnu_debuglink or .gnu_debugaltlink sections. Add a --debug-dump=follow-links option to readelf and a --dwarf=follow-links option to objdump which causes indirect links into separate debug info files to be followed when dumping other DWARF sections. - Add support for loaction views in DWARF debug line information. - Add -z separate-code to generate separate code PT_LOAD segment. - Add quot;-z undefsquot; command line option as the inverse of the quot;-z defsquot; option. - Add -z globalaudit command line option to force audit libraries to be run for every dynamic object loaded by an executable - provided that the loader supports this functionality. - Tighten linker script grammar around file name specifiers to prevent the use of SORT_BY_ALIGNMENT and SORT_BY_INIT_PRIORITY on filenames. These would previously be accepted but had no effect. - The EXCLUDE_FILE directive can now be placed within any SORT_* directive within input section lists. - Fix linker relaxation with --wrap - Add arm-none-eabi symlinks Former updates of binutils also fixed the following security issues, for which there was not CVE assigned at the time the update was released or no mapping between code change and CVE existed: - CVE-2014-9939: Prevent stack buffer overflow when printing bad bytes in Intel Hex objects . - CVE-2017-7225: The find_nearest_line function in addr2line did not handle the case where the main file name and the directory name are both empty, triggering a NULL pointer dereference and an invalid write, and leading to a program crash . - CVE-2017-7224: The find_nearest_line function in objdump was vulnerable to an invalid write while disassembling a corrupt binary that contains an empty function name, leading to a program crash . - CVE-2017-7223: GNU assembler in was vulnerable to a global buffer overflow while attempting to unget an EOF character from the input stream, potentially leading to a program crash . - CVE-2017-7226: The pe_ILF_object_p function in the Binary File Descriptor library was vulnerable to a heap-based buffer over-read of size 4049 because it used the strlen function instead of strnlen, leading to program crashes in several utilities such as addr2line, size, and strings. It could lead to information disclosure as well . - CVE-2017-7299: The Binary File Descriptor library had an invalid read because the code to emit relocs did not check the format of the input file trying to read the ELF reloc section header. The vulnerability leads to a GNU linker program crash . - CVE-2017-7300: The Binary File Descriptor library had an aout_link_add_symbols function in bfd/aoutx.h that is vulnerable to a heap-based buffer over-read because of an incomplete check for invalid string offsets while loading symbols, leading to a GNU linker program crash . - CVE-2017-7302: The Binary File Descriptor library had a swap_std_reloc_out function in bfd/aoutx.h that is vulnerable to an invalid read because of missing checks for relocs that could not be recognised. This vulnerability caused Binutils utilities like strip to crash . - CVE-2017-7303: The Binary File Descriptor library was vulnerable to an invalid read because of missing a check for null headers attempting to match them. This vulnerability caused Binutils utilities like strip to crash . - CVE-2017-7301: The Binary File Descriptor library had an aout_link_add_symbols function in bfd/aoutx.h that has an off-by-one vulnerability because it did not carefully check the string offset. The vulnerability could lead to a GNU linker program crash . - CVE-2017-7304: The Binary File Descriptor library was vulnerable to an invalid read because of missing a check for an invalid sh_link field attempting to follow it. This vulnerability caused Binutils utilities like strip to crash . - CVE-2017-8392: The Binary File Descriptor library was vulnerable to an invalid read of size 8 because of missing a check to determine whether symbols are NULL in the _bfd_dwarf2_find_nearest_line function. This vulnerability caused programs that conduct an analysis of binary programs using the libbfd library, such as objdump, to crash . - CVE-2017-8393: The Binary File Descriptor library was vulnerable to a global buffer over-read error because of an assumption made by code that runs for objcopy and strip, that SHT_REL/SHR_RELA sections are always named starting with a .rel/.rela prefix. This vulnerability caused programs that conduct an analysis of binary programs using the libbfd library, such as objcopy and strip, to crash . - CVE-2017-8394: The Binary File Descriptor library was vulnerable to an invalid read of size 4 due to NULL pointer dereferencing of _bfd_elf_large_com_section. This vulnerability caused programs that conduct an analysis of binary programs using the libbfd library, such as objcopy, to crash . - CVE-2017-8396: The Binary File Descriptor library was vulnerable to an invalid read of size 1 because the existing reloc offset range tests didn"t catch small negative offsets less than the size of the reloc field. This vulnerability caused programs that conduct an analysis of binary programs using the libbfd library, such as objdump, to crash . - CVE-2017-8421: The function coff_set_alignment_hook in Binary File Descriptor library had a memory leak vulnerability which can cause memory exhaustion in objdump via a crafted PE file . - CVE-2017-9746: The disassemble_bytes function in objdump.c allowed remote attackers to cause a denial of service or possibly have unspecified other impact via a crafted binary file, as demonstrated by mishandling of rae insns printing for this file during quot;objdump -Dquot; execution . - CVE-2017-9747: The ieee_archive_p function in the Binary File Descriptor library might have allowed remote attackers to cause a denial of service or possibly have unspecified other impact via a crafted binary file, as demonstrated by mishandling of this file during quot;objdump -Dquot; execution . - CVE-2017-9748: The ieee_object_p function in the Binary File Descriptor library might have allowed remote attackers to cause a denial of service or possibly have unspecified other impact via a crafted binary file, as demonstrated by mishandling of this file during quot;objdump -Dquot; execution . - CVE-2017-9750: opcodes/rx-decode.opc lacked bounds checks for certain scale arrays, which allowed remote attackers to cause a denial of service or possibly have unspecified other impact via a crafted binary file, as demonstrated by mishandling of this file during quot;objdump -Dquot; execution . - CVE-2017-9755: Not considering the the number of registers for bnd mode allowed remote attackers to cause a denial of service or possibly have unspecified other impact via a crafted binary file, as demonstrated by mishandling of this file during quot;objdump -Dquot; execution . - CVE-2017-9756: The aarch64_ext_ldst_reglist function allowed remote attackers to cause a denial of service or possibly have unspecified other impact via a crafted binary file, as demonstrated by mishandling of this file during quot;objdump -Dquot; execution . - CVE-2017-7209: The dump_section_as_bytes function in readelf accessed a NULL pointer while reading section contents in a corrupt binary, leading to a program crash . - CVE-2017-6965: readelf wrote to illegal addresses while processing corrupt input files containing symbol-difference relocations, leading to a heap-based buffer overflow . - CVE-2017-6966: readelf had a use-after-free error while processing multiple, relocated sections in an MSP430 binary. This is caused by mishandling of an invalid symbol index, and mishandling of state across invocations . - CVE-2017-6969: readelf was vulnerable to a heap-based buffer over-read while processing corrupt RL78 binaries. The vulnerability can trigger program crashes. It may lead to an information leak as well . - CVE-2017-7210: objdump was vulnerable to multiple heap-based buffer over-reads while handling corrupt STABS enum type strings in a crafted object file, leading to program crash .