bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug binutils/17512] libbfd/binutils: crashes on fuzzed samples


From: cvs-commit at gcc dot gnu.org
Subject: [Bug binutils/17512] libbfd/binutils: crashes on fuzzed samples
Date: Tue, 10 Feb 2015 14:12:23 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=17512

--- Comment #197 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot 
gnu.org> ---
The master branch has been updated by Nick Clifton <address@hidden>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=77ef86547510cee3a2bff27bea9f19f0b2715bae

commit 77ef86547510cee3a2bff27bea9f19f0b2715bae
Author: Nick Clifton <address@hidden>
Date:   Tue Feb 10 14:11:00 2015 +0000

    Fix memory access violations triggered by running objdump compiled with
out-of-bounds sanitization checking.

        PR binutils/17512
        * dwarf.c (eh_addr_size): Use an unsigned type.
        (size_of_encoded_value): Return an unsigned type.
        (read_leb128): Break if the shift becomes too big.
        (process_extended_line_op): Do not read the address if the length
        is too long.
        (read_cie): Warn and fail if the pointer size or segment size are
        too big.
        * dwarf.h (DWARF2_External_LineInfo): Delete unused and incorrect
        structure definition.
        (DWARF2_External_PubNames): Likewise.
        (DWARF2_External_CompUnit): Likewise.
        (DWARF2_External_ARange): Likewise.
        (DWARF2_Internal_LineInfo): Use dwarf_vma type for
        li_prologue_length.
        (eh_addr_size): Update prototype.

        * coffcode.h (styp_to_sec_flags): Use an unsigned long type to
        hold the flag bits.
        * peXXigen.c (pe_print_reloc): Use unsigned types to hold the
        size and number of relocs.
        (pe_print_debugdata): Use a 32-bit aligned buffer to store the
        codeview record.
        * versados.c (process_otr): Check the esdid value before using it
        to access the EDATA.

-- 
You are receiving this mail because:
You are on the CC list for the bug.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]