Issue 46479 in oss-fuzz: binutils: Fuzzing build failure

2022-04-07 Thread davia monorail
Comment #1 on issue 46479 by da...@adalogics.com: binutils: Fuzzing build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=46479#c1 This is fixed with https://github.com/google/oss-fuzz/pull/7527 -- You received this message because: 1. You were specifically CC'd on the issue Y

Issue 43790 in oss-fuzz: binutils:fuzz_as: Null-dereference READ in htab_find_slot

2022-03-19 Thread davia monorail
Comment #3 on issue 43790 by da...@adalogics.com: binutils:fuzz_as: Null-dereference READ in htab_find_slot https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=43790#c3 Fuzzer fix in https://github.com/google/oss-fuzz/pull/7402 -- You received this message because: 1. You were specifically

Issue 41628 in oss-fuzz: binutils: Fuzzing build failure

2021-12-03 Thread davia monorail
Comment #1 on issue 41628 by da...@adalogics.com: binutils: Fuzzing build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=41628#c1 This s a false positive. All AFL build are failing right now. https://github.com/google/oss-fuzz/issues/6957 Apologies for inconvenience -- You rec

Issue 40837 in oss-fuzz: binutils:fuzz_addr2line: Dynamic-stack-buffer-overflow in error_handler_internal

2021-11-08 Thread davia monorail
Comment #3 on issue 40837 by da...@adalogics.com: binutils:fuzz_addr2line: Dynamic-stack-buffer-overflow in error_handler_internal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=40837#c3 I'm unable to reproduce this one -- You received this message because: 1. You were specifically CC

Issue 40618 in oss-fuzz: binutils:fuzz_objdump_safe: Dynamic-stack-buffer-overflow in error_handler_internal

2021-11-02 Thread davia monorail
Comment #3 on issue 40618 by da...@adalogics.com: binutils:fuzz_objdump_safe: Dynamic-stack-buffer-overflow in error_handler_internal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=40618#c3 AFL build fix has been deployed, this should be automatically closed shortly. -- You received thi

Issue 40632 in oss-fuzz: binutils:fuzz_readelf: Dynamic-stack-buffer-overflow in unw_decode_r3

2021-11-02 Thread davia monorail
Comment #2 on issue 40632 by da...@adalogics.com: binutils:fuzz_readelf: Dynamic-stack-buffer-overflow in unw_decode_r3 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=40632#c2 This is a false positive for similar reasons as https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=40620 Apo

Issue 40618 in oss-fuzz: binutils:fuzz_objdump_safe: Dynamic-stack-buffer-overflow in error_handler_internal

2021-11-02 Thread davia monorail
Comment #2 on issue 40618 by da...@adalogics.com: binutils:fuzz_objdump_safe: Dynamic-stack-buffer-overflow in error_handler_internal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=40618#c2 This is a false positive for similar reasons as https://bugs.chromium.org/p/oss-fuzz/issues/detail

Issue 40620 in oss-fuzz: binutils:fuzz_disas_ext-bfd_arch_i386: Dynamic-stack-buffer-overflow in fetch_data

2021-11-02 Thread davia monorail
Comment #3 on issue 40620 by da...@adalogics.com: binutils:fuzz_disas_ext-bfd_arch_i386: Dynamic-stack-buffer-overflow in fetch_data https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=40620#c3 I debugged this more and it is a false positive due to the AFL build getting messed up. A fix wa

Issue 40620 in oss-fuzz: binutils:fuzz_disas_ext-bfd_arch_i386: Dynamic-stack-buffer-overflow in fetch_data

2021-11-02 Thread davia monorail
Comment #1 on issue 40620 by da...@adalogics.com: binutils:fuzz_disas_ext-bfd_arch_i386: Dynamic-stack-buffer-overflow in fetch_data https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=40620#c1 Am not entirely sure what's going on here. I am unable to reproduce the issue with libFuzzer or ho

Issue 40330 in oss-fuzz: binutils:fuzz_as: Stack-use-after-return in as_bad_internal

2021-10-27 Thread davia monorail
Comment #7 on issue 40330 by da...@adalogics.com: binutils:fuzz_as: Stack-use-after-return in as_bad_internal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=40330#c7 Thanks for the info! The reason by and large is that OSS-Fuzz does not support fork-based fuzzing. It would be ideal if

Issue 40330 in oss-fuzz: binutils:fuzz_as: Stack-use-after-return in as_bad_internal

2021-10-26 Thread davia monorail
Comment #2 on issue 40330 by da...@adalogics.com: binutils:fuzz_as: Stack-use-after-return in as_bad_internal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=40330#c2 Thanks for the analysis. I see two approaches forward, either come up with some solution in the fuzzer that resets all of

Issue 40330 in oss-fuzz: binutils:fuzz_as: Stack-use-after-return in as_bad_internal

2021-10-26 Thread davia monorail
Comment #4 on issue 40330 by da...@adalogics.com: binutils:fuzz_as: Stack-use-after-return in as_bad_internal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=40330#c4 You're right. However, it would be great being able to fuzz the main logic in libbfd that gas uses so I will try to see h

Issue 40248 in oss-fuzz: binutils:fuzz_objdump: Heap-buffer-overflow in bfd_mach_o_arm_canonicalize_one_reloc

2021-10-25 Thread davia monorail
Comment #2 on issue 40248 by da...@adalogics.com: binutils:fuzz_objdump: Heap-buffer-overflow in bfd_mach_o_arm_canonicalize_one_reloc https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=40248#c2 I think a fix was made here https://github.com/bminor/binutils-gdb/commit/e02812494254b70fec6fa43

Issue 40233 in oss-fuzz: binutils:fuzz_nm: Heap-buffer-overflow in aout_get_external_symbols

2021-10-25 Thread davia monorail
Comment #3 on issue 40233 by da...@adalogics.com: binutils:fuzz_nm: Heap-buffer-overflow in aout_get_external_symbols https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=40233#c3 https://github.com/bminor/binutils-gdb/commit/3f9661f12a42583c91655bc5c5b60542bcaed4e2 -- You received this messa

Issue 40280 in oss-fuzz: binutils:fuzz_objdump: Null-dereference READ in bfd_nonfatal_message

2021-10-25 Thread davia monorail
Comment #2 on issue 40280 by da...@adalogics.com: binutils:fuzz_objdump: Null-dereference READ in bfd_nonfatal_message https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=40280#c2 This was an issue in the fuzzer itself, fix proposed and merge here: https://github.com/google/oss-fuzz/commit/f2

Issue 21180 in oss-fuzz

2020-03-14 Thread davia monorail
The following issue was updated: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=21180#c3 -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to ad