-libelf
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68719
Detailed Report: https://oss-fuzz.com/testcase?key=5344202996121600
Project: elfutils
Fuzzing Engine: libFuzzer
Fuzz Target: fuzz-libelf
Job Type: libfuzzer_asan_i386_elfutils
Platform Id: linux
Crash Type: Timeout (exceeds 60 secs
Updates:
Labels: ClusterFuzz-Verified
Status: Verified
Comment #1 on issue 53588 by ClusterFuzz-External: elfutils:fuzz-libelf:
Timeout in fuzz-libelf
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=53588#c1
ClusterFuzz testcase 5208347720941568 is verified as fixed in
Comment #4 on issue 62071 by ClusterFuzz-External: elfutils:fuzz-libdwfl:
Null-dereference READ in chunk_compare
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=62071#c4
ClusterFuzz testcase 5999675550072832 is closed as invalid, so closing issue.
--
You received this message because
Updates:
Status: WontFix
Comment #3 on issue 62071 by ClusterFuzz-External: elfutils:fuzz-libdwfl:
Null-dereference READ in chunk_compare
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=62071#c3
ClusterFuzz testcase 5999675550072832 is flaky and no longer crashes, so
closing
Hi,
On Thu, Sep 07, 2023 at 04:25:00PM +0200, Mark Wielaard wrote:
> Subject: [PATCH] libelf: tdelete dummy key if anything goes wrong setting up
> rawchunk
>
> elf_getdata_rawchunk uses a binary search tree cache. If a rawchunk is
> not yet in the cache we setup a new entry. But if anything wen
On Thu, 2023-09-07 at 06:23 -0700, evv… via monorail via Elfutils-devel
wrote:
> Comment #2 on issue 62071 by evv...@gmail.com: elfutils:fuzz-libdwfl:
> Null-dereference READ in chunk_compare
> https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=62071#c2
>
> For some reason the
Comment #2 on issue 62071 by evv...@gmail.com: elfutils:fuzz-libdwfl:
Null-dereference READ in chunk_compare
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=62071#c2
For some reason the testcase isn't public. I'll report it to OSS-Fuzz.
I uploaded the test case to GitHub
Hi Evgeny,
On Thu, 2023-09-07 at 05:31 -0700, evv… via monorail via Elfutils-devel
wrote:
> Comment #1 on issue 62071 by evv...@gmail.com: elfutils:fuzz-libdwfl:
> Null-dereference READ in chunk_compare
> https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=62071#c1
>
> ```
Comment #1 on issue 62071 by evv...@gmail.com: elfutils:fuzz-libdwfl:
Null-dereference READ in chunk_compare
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=62071#c1
```
SCARINESS: 10 (null-deref)
#0 0x82d35d1 in chunk_compare
/src/elfutils/libelf/elf_getdata_rawchunk.c:49:25
#1
ddressSanitizer Unreproducible
> Engine-libfuzzer OS-Linux Proj-elfutils Reported-2023-09-06
> Type: Bug
>
> New issue 62071 by ClusterFuzz-External: elfutils:fuzz-libdwfl:
> Null-dereference READ in chunk_compare
> https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=62071
>
>
: elfutils:fuzz-libdwfl:
Null-dereference READ in chunk_compare
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=62071
Detailed Report: https://oss-fuzz.com/testcase?key=5999675550072832
Project: elfutils
Fuzzing Engine: libFuzzer
Fuzz Target: fuzz-libdwfl
Job Type: libfuzzer_asan_i386_elfutils
Updates:
Labels: ClusterFuzz-Verified
Status: Verified
Comment #2 on issue 60887 by ClusterFuzz-External: elfutils:fuzz-libelf:
Direct-leak in __libelf_decompress_zlib
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=60887#c2
ClusterFuzz testcase 4651173658099712 is
Hi,
On Sat, Jul 29, 2023 at 03:00:49PM -0700, evv… via monorail via Elfutils-devel
wrote:
>
> Comment #1 on issue 60887 by evv...@gmail.com: elfutils:fuzz-libelf:
> Direct-leak in __libelf_decompress_zlib
> https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=60887#c1
>
>
Comment #1 on issue 60887 by evv...@gmail.com: elfutils:fuzz-libelf:
Direct-leak in __libelf_decompress_zlib
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=60887#c1
The full backtrace is
```
==178009==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 1 byte(s) in 1 object(s
20220317
>
> Reproducer Testcase:
> https://oss-fuzz.com/download?testcase_id=4651173658099712
>
> Issue filed automatically.
>
> See https://google.github.io/oss-fuzz/advanced-topics/reproducing for
> instructions to reproduce this bug locally.
> When you fix th
by ClusterFuzz-External: elfutils:fuzz-libelf: Direct-leak in
__libelf_decompress_zlib
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=60887
Detailed Report: https://oss-fuzz.com/testcase?key=4651173658099712
Project: elfutils
Fuzzing Engine: libFuzzer
Fuzz Target: fuzz-libelf
Job Type
-libdwfl
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=59033
Detailed Report: https://oss-fuzz.com/testcase?key=5094017457848320
Project: elfutils
Fuzzing Engine: libFuzzer
Fuzz Target: fuzz-libdwfl
Job Type: libfuzzer_ubsan_elfutils
Platform Id: linux
Crash Type: Timeout (exceeds 60 secs
Updates:
Labels: ClusterFuzz-Verified
Status: Verified
Comment #1 on issue 46515 by ClusterFuzz-External: elfutils:fuzz-libdwfl:
Timeout in fuzz-libdwfl
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=46515#c1
ClusterFuzz testcase 6105086314545152 is verified as fixed in
Updates:
Status: WontFix
Comment #4 on issue 56134 by ClusterFuzz-External: elfutils:fuzz-libdwfl:
Use-of-uninitialized-value in check_section
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=56134#c4
ClusterFuzz testcase 6724057145147392 is flaky and no longer crashes, so
closing
Comment #5 on issue 56134 by ClusterFuzz-External: elfutils:fuzz-libdwfl:
Use-of-uninitialized-value in check_section
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=56134#c5
ClusterFuzz testcase 6724057145147392 is closed as invalid, so closing issue.
--
You received this message
Updates:
Labels: ClusterFuzz-Verified
Status: Verified
Comment #2 on issue 56179 by ClusterFuzz-External: elfutils:fuzz-libdwfl:
Use-of-uninitialized-value in check_section
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=56179#c2
ClusterFuzz testcase 6538272475316224 is
Updates:
Labels: -Reproducible Unreproducible
Comment #3 on issue 56134 by ClusterFuzz-External: elfutils:fuzz-libdwfl:
Use-of-uninitialized-value in check_section
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=56134#c3
ClusterFuzz testcase 6724057145147392 appears to be flaky
Comment #1 on issue 56179 by evv...@gmail.com: elfutils:fuzz-libdwfl:
Use-of-uninitialized-value in check_section
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=56179#c1
It's a duplicate of https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=56134
as far as I can tell. I'
56179 by ClusterFuzz-External: elfutils:fuzz-libdwfl:
Use-of-uninitialized-value in check_section
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=56179
Detailed Report: https://oss-fuzz.com/testcase?key=6538272475316224
Project: elfutils
Fuzzing Engine: libFuzzer
Fuzz Target: fuzz-libdwfl
Job
Comment #1 on issue 56134 by evv...@gmail.com: elfutils:fuzz-libdwfl:
Use-of-uninitialized-value in check_section
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=56134#c1
Below is the full backtrace
```
==2272==WARNING: MemorySanitizer: use-of-uninitialized-value
#0 0x5fb3c7 in
Comment #2 on issue 56134 by evv...@gmail.com: elfutils:fuzz-libdwfl:
Use-of-uninitialized-value in check_section
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=56134#c2
It can be confirmed with Valgrind:
```
wget -O OSS-FUZZ-56134
'https://oss-fuzz.com/download?testca
56134 by ClusterFuzz-External: elfutils:fuzz-libdwfl:
Use-of-uninitialized-value in check_section
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=56134
Detailed Report: https://oss-fuzz.com/testcase?key=6724057145147392
Project: elfutils
Fuzzing Engine: libFuzzer
Fuzz Target: fuzz-libdwfl
Job
Updates:
Status: Verified
Comment #1 on issue 56085 by ClusterFuzz-External: elfutils: Fuzzing build
failure
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=56085#c1
The latest build has succeeded, closing this issue.
--
You received this message because:
1. You were
Hi Mark,
> You probably
> don't have libstdc++-devel in your setup. If you cannot install that
> you now have to explicitly configure with --disable-demangler.
Thanks! I opened https://github.com/google/oss-fuzz/pull/9745 where I turned
the demangler off.
libstdc++-dev was ind
.@gmail.com,
> izz...@google.com
> Labels: Proj-elfutils
> Type: Build-Failure
>
> New issue 56085 by ClusterFuzz-External: elfutils: Fuzzing build failure
> https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=56085
>
> The last 3 builds for elfutils have been fail
Status: New
Owner:
CC: elfut...@sourceware.org, da...@adalogics.com, evv...@gmail.com,
izz...@google.com
Labels: Proj-elfutils
Type: Build-Failure
New issue 56085 by ClusterFuzz-External: elfutils: Fuzzing build failure
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=56085
The last
Hi Mark,
> Why can't you simply use the configure support?
I can't interfere with CFLAGS/CXXFLAGS passed by OSS-Fuzz. For example if
I used `--enable-sanitize-undefined` I would overwrite all the
`-fsanitize=...` and
`-fno-sanitize-recover=...` flags used by OSS-Fuzz. I also embed
Hi Evgeny,
On Wed, 2023-02-15 at 20:07 +0300, Evgeny Vereshchagin via Elfutils-
devel wrote:
> I fixed the build failure in
> https://github.com/google/oss-fuzz/pull/9718. Once it's merged
> and reaches ClusterFuzz OSS-Fuzz should close the issue.
Thanks. That seems to have wor
Updates:
Status: Verified
Comment #1 on issue 55999 by ClusterFuzz-External: elfutils: Fuzzing build
failure
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=55999#c1
The latest build has succeeded, closing this issue.
--
You received this message because:
1. You were
Hi Mark,
I fixed the build failure in
https://github.com/google/oss-fuzz/pull/9718. Once it's merged
and reaches ClusterFuzz OSS-Fuzz should close the issue.
> Note that we also recently got support for --enable-sanitize-memory but
> that needs a bit of setup and only works wit
ogics.com, evv...@gmail.com,
> izz...@google.com
> Labels: Proj-elfutils
> Type: Build-Failure
>
> New issue 55999 by ClusterFuzz-External: elfutils: Fuzzing build failure
> https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=55999
>
> The last 3 builds for elfutils have been fai
Status: New
Owner:
CC: elfut...@sourceware.org, da...@adalogics.com, evv...@gmail.com,
izz...@google.com
Labels: Proj-elfutils
Type: Build-Failure
New issue 55999 by ClusterFuzz-External: elfutils: Fuzzing build failure
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=55999
The last
-libelf
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=53588
Detailed Report: https://oss-fuzz.com/testcase?key=5208347720941568
Project: elfutils
Fuzzing Engine: libFuzzer
Fuzz Target: fuzz-libelf
Job Type: libfuzzer_asan_i386_elfutils
Platform Id: linux
Crash Type: Timeout (exceeds 60 secs
Updates:
Labels: ClusterFuzz-Verified
Status: Verified
Comment #1 on issue 49759 by ClusterFuzz-External: elfutils:fuzz-libelf:
Timeout in fuzz-libelf
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=49759#c1
ClusterFuzz testcase 4741251823435776 is verified as fixed in
Updates:
Status: Verified
Comment #1 on issue 50751 by ClusterFuzz-External: elfutils: Fuzzing build
failure
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=50751#c1
The latest build has succeeded, closing this issue.
--
You received this message because:
1. You were
Status: New
Owner:
CC: elfut...@sourceware.org, da...@adalogics.com, evv...@gmail.com,
izz...@google.com
Labels: Proj-elfutils
Type: Build-Failure
New issue 50751 by ClusterFuzz-External: elfutils: Fuzzing build failure
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=50751
The last
-libelf
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=49759
Detailed Report: https://oss-fuzz.com/testcase?key=4741251823435776
Project: elfutils
Fuzzing Engine: libFuzzer
Fuzz Target: fuzz-libelf
Job Type: libfuzzer_asan_i386_elfutils
Platform Id: linux
Crash Type: Timeout (exceeds 60 secs
Updates:
Labels: ClusterFuzz-Verified
Status: Verified
Comment #1 on issue 47421 by ClusterFuzz-External: elfutils:fuzz-libelf:
Timeout in fuzz-libelf
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=47421#c1
ClusterFuzz testcase 5573250354118656 is verified as fixed in
fuzz-libdwfl
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=47839
Detailed Report: https://oss-fuzz.com/testcase?key=5667684760551424
Project: elfutils
Fuzzing Engine: libFuzzer
Fuzz Target: fuzz-libdwfl
Job Type: libfuzzer_asan_elfutils
Platform Id: linux
Crash Type: Out-of-memory
Updates:
Labels: ClusterFuzz-Verified
Status: Verified
Comment #1 on issue 46513 by ClusterFuzz-External: elfutils:fuzz-libdwfl:
Out-of-memory in fuzz-libdwfl
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=46513#c1
ClusterFuzz testcase 5920608711475200 is verified as
-libelf
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=47421
Detailed Report: https://oss-fuzz.com/testcase?key=5573250354118656
Project: elfutils
Fuzzing Engine: libFuzzer
Fuzz Target: fuzz-libelf
Job Type: libfuzzer_asan_i386_elfutils
Platform Id: linux
Crash Type: Timeout (exceeds 60 secs
Updates:
Labels: ClusterFuzz-Verified
Status: Verified
Comment #1 on issue 46898 by ClusterFuzz-External: elfutils:fuzz-libelf:
Timeout in fuzz-libelf
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=46898#c1
ClusterFuzz testcase 6521986165112832 is verified as fixed in
-libelf
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=46898
Detailed Report: https://oss-fuzz.com/testcase?key=6521986165112832
Project: elfutils
Fuzzing Engine: libFuzzer
Fuzz Target: fuzz-libelf
Job Type: libfuzzer_asan_i386_elfutils
Platform Id: linux
Crash Type: Timeout (exceeds 60 secs
-libdwfl
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=46515
Detailed Report: https://oss-fuzz.com/testcase?key=6105086314545152
Project: elfutils
Fuzzing Engine: libFuzzer
Fuzz Target: fuzz-libdwfl
Job Type: libfuzzer_ubsan_elfutils
Platform Id: linux
Crash Type: Timeout (exceeds 60 secs
fuzz-libdwfl
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=46513
Detailed Report: https://oss-fuzz.com/testcase?key=5920608711475200
Project: elfutils
Fuzzing Engine: libFuzzer
Fuzz Target: fuzz-libdwfl
Job Type: libfuzzer_asan_elfutils
Platform Id: linux
Crash Type: Out-of-memory
Comment #7 on issue 45630 by ClusterFuzz-External: elfutils:fuzz-libelf:
Use-of-uninitialized-value in validate_str
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45630#c7
ClusterFuzz testcase 5658767587409920 is closed as invalid, so closing issue.
--
You received this message
Updates:
Status: WontFix
Comment #6 on issue 45630 by ClusterFuzz-External: elfutils:fuzz-libelf:
Use-of-uninitialized-value in validate_str
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45630#c6
ClusterFuzz testcase 5658767587409920 is flaky and no longer crashes, so
closing
Updates:
Labels: ClusterFuzz-Verified
Status: Verified
Comment #1 on issue 46192 by ClusterFuzz-External: elfutils:fuzz-libdwfl:
Out-of-memory in fuzz-libdwfl
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=46192#c1
ClusterFuzz testcase 5364854623436800 is verified as
Hi,
On Wed, Mar 30, 2022 at 03:24:17PM -0700, ClusterFuzz-External via monorail via
Elfutils-devel wrote:
> New issue 46192 by ClusterFuzz-External: elfutils:fuzz-libdwfl: Out-of-memory
> in fuzz-libdwfl
> https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=46192
>
> Detaile
fuzz-libdwfl
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=46192
Detailed Report: https://oss-fuzz.com/testcase?key=5364854623436800
Project: elfutils
Fuzzing Engine: libFuzzer
Fuzz Target: fuzz-libdwfl
Job Type: libfuzzer_asan_elfutils
Platform Id: linux
Crash Type: Out-of-memory
Updates:
Labels: ClusterFuzz-Verified
Status: Verified
Comment #2 on issue 46094 by ClusterFuzz-External: elfutils:fuzz-libdwfl:
Use-of-uninitialized-value in elf_compress_gnu
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=46094#c2
ClusterFuzz testcase 4725021634854912 is
Updates:
Labels: ClusterFuzz-Verified
Status: Verified
Comment #2 on issue 46095 by ClusterFuzz-External: elfutils:fuzz-libelf:
Use-of-uninitialized-value in elf_compress_gnu
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=46095#c2
ClusterFuzz testcase 6467719510228992 is
Comment #1 on issue 46095 by evv...@gmail.com: elfutils:fuzz-libelf:
Use-of-uninitialized-value in elf_compress_gnu
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=46095#c1
It was reported in https://sourceware.org/bugzilla/show_bug.cgi?id=29000 as
well. To avoid duplicates like this
46095 by ClusterFuzz-External: elfutils:fuzz-libelf:
Use-of-uninitialized-value in elf_compress_gnu
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=46095
Detailed Report: https://oss-fuzz.com/testcase?key=6467719510228992
Project: elfutils
Fuzzing Engine: libFuzzer
Fuzz Target: fuzz-libelf
Job
Comment #1 on issue 46094 by evv...@gmail.com: elfutils:fuzz-libdwfl:
Use-of-uninitialized-value in elf_compress_gnu
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=46094#c1
It was reported in https://sourceware.org/bugzilla/show_bug.cgi?id=29000
--
You received this message because
46094 by ClusterFuzz-External: elfutils:fuzz-libdwfl:
Use-of-uninitialized-value in elf_compress_gnu
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=46094
Detailed Report: https://oss-fuzz.com/testcase?key=4725021634854912
Project: elfutils
Fuzzing Engine: libFuzzer
Fuzz Target: fuzz-libdwfl
Updates:
Labels: ClusterFuzz-Verified
Status: Verified
Comment #1 on issue 45633 by ClusterFuzz-External: elfutils:fuzz-libdwfl:
Use-of-uninitialized-value in __libelf_read_mmaped_file
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45633#c1
ClusterFuzz testcase
Updates:
Labels: ClusterFuzz-Verified
Status: Verified
Comment #4 on issue 45631 by ClusterFuzz-External: elfutils:fuzz-libdwfl:
Use-of-uninitialized-value in __libdw_gunzip
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45631#c4
ClusterFuzz testcase 5742116662280192 is
Updates:
Labels: -Reproducible Unreproducible
Comment #5 on issue 45630 by ClusterFuzz-External: elfutils:fuzz-libelf:
Use-of-uninitialized-value in validate_str
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45630#c5
ClusterFuzz testcase 5658767587409920 appears to be flaky
Updates:
Labels: ClusterFuzz-Verified
Status: Verified
Comment #1 on issue 45952 by ClusterFuzz-External: elfutils:fuzz-libdwfl:
Misaligned-address in elf_cvt_gnuhash
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45952#c1
ClusterFuzz testcase 6331966935400448 is verified
Updates:
Labels: ClusterFuzz-Verified
Status: Verified
Comment #5 on issue 43505 by ClusterFuzz-External: elfutils:fuzz-dwfl-core:
Use-of-uninitialized-value in handle_file_note
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=43505#c5
ClusterFuzz testcase 5344860645752832
Updates:
Labels: ClusterFuzz-Verified
Status: Verified
Comment #1 on issue 45676 by ClusterFuzz-External: elfutils:fuzz-libdwfl:
Use-of-uninitialized-value in dwfl_report_module
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45676#c1
ClusterFuzz testcase 6448716024774656
Updates:
Labels: ClusterFuzz-Verified
Status: Verified
Comment #1 on issue 45647 by ClusterFuzz-External: elfutils:fuzz-libdwfl:
Use-of-uninitialized-value in find_debuginfo_in_path
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45647#c1
ClusterFuzz testcase
Updates:
Labels: ClusterFuzz-Verified
Status: Verified
Comment #2 on issue 45706 by ClusterFuzz-External: elfutils:fuzz-libdwfl:
Use-of-uninitialized-value in process_file
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45706#c2
ClusterFuzz testcase 5736328928559104 is
Updates:
Labels: Fuzz-Blocker
Comment #3 on issue 45631 by ClusterFuzz-External: elfutils:fuzz-libdwfl:
Use-of-uninitialized-value in __libdw_gunzip
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45631#c3
This crash occurs very frequently on linux platform and is likely
Comment #1 on issue 45706 by evv...@gmail.com: elfutils:fuzz-libdwfl:
Use-of-uninitialized-value in process_file
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45706#c1
It's a false positive. https://github.com/google/oss-fuzz/pull/7422 should fix
it.
--
You received this me
: elfutils:fuzz-libdwfl:
Misaligned-address in elf_cvt_gnuhash
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45952
Detailed Report: https://oss-fuzz.com/testcase?key=6331966935400448
Project: elfutils
Fuzzing Engine: libFuzzer
Fuzz Target: fuzz-libdwfl
Job Type: libfuzzer_ubsan_elfutils
Updates:
Labels: ClusterFuzz-Verified
Status: Verified
Comment #3 on issue 45637 by ClusterFuzz-External: elfutils:fuzz-libelf:
Timeout in fuzz-libelf
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45637#c3
ClusterFuzz testcase 6393240885002240 is verified as fixed in
Updates:
Labels: ClusterFuzz-Verified
Status: Verified
Comment #4 on issue 45636 by ClusterFuzz-External: elfutils:fuzz-libdwfl: Crash
in read_long_names
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45636#c4
ClusterFuzz testcase 5787862593830912 is verified as fixed in
Updates:
Labels: ClusterFuzz-Verified
Status: Verified
Comment #3 on issue 45646 by ClusterFuzz-External: elfutils:fuzz-libdwfl:
Misaligned-address in __libdw_image_header
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45646#c3
ClusterFuzz testcase 5699171619831808 is
Updates:
Labels: ClusterFuzz-Verified
Status: Verified
Comment #4 on issue 45629 by ClusterFuzz-External: elfutils:fuzz-libdwfl:
Indirect-leak in __libelf_read_mmaped_file
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45629#c4
ClusterFuzz testcase 5280476447768576 is
Updates:
Labels: ClusterFuzz-Verified
Status: Verified
Comment #3 on issue 45635 by ClusterFuzz-External: elfutils:fuzz-libdwfl:
Timeout in fuzz-libdwfl
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45635#c3
ClusterFuzz testcase 5237809772888064 is verified as fixed in
Updates:
Labels: ClusterFuzz-Verified
Status: Verified
Comment #6 on issue 45705 by ClusterFuzz-External: elfutils:fuzz-libdwfl:
Indirect-leak in __libelf_next_arhdr_wrlock
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45705#c6
ClusterFuzz testcase 5085329692950528 is
Updates:
Labels: ClusterFuzz-Verified
Status: Verified
Comment #3 on issue 45634 by ClusterFuzz-External: elfutils:fuzz-libdwfl:
Misaligned-address in file_read_elf
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45634#c3
ClusterFuzz testcase 5069818166902784 is verified
Updates:
Labels: ClusterFuzz-Verified
Status: Verified
Comment #3 on issue 45682 by ClusterFuzz-External: elfutils:fuzz-libelf:
Misaligned-address in elf_cvt_Verneed
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45682#c3
ClusterFuzz testcase 4968585519300608 is verified
Updates:
Labels: ClusterFuzz-Verified
Status: Verified
Comment #5 on issue 45628 by ClusterFuzz-External: elfutils:fuzz-libdwfl:
Heap-buffer-overflow in strtol
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45628#c5
ClusterFuzz testcase 4673586076450816 is verified as
Comment #5 on issue 45705 by evv...@gmail.com: elfutils:fuzz-libdwfl:
Indirect-leak in __libelf_next_arhdr_wrlock
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45705#c5
> I did this because I asked in an internal email with Mark if it would be
> appreciated (the answer w
Comment #4 on issue 45705 by da...@adalogics.com: elfutils:fuzz-libdwfl:
Indirect-leak in __libelf_next_arhdr_wrlock
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45705#c4
Yes -- I did this because I asked in an internal email with Mark if it would be
appreciated (the answer was yet
Comment #3 on issue 45705 by evv...@gmail.com: elfutils:fuzz-libdwfl:
Indirect-leak in __libelf_next_arhdr_wrlock
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45705#c3
Reproducer testcases are publicly available and can be downloaded using links
in bug reports. Since every comment is
Comment #4 on issue 45630 by evv...@gmail.com: elfutils:fuzz-libelf:
Use-of-uninitialized-value in validate_str
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45630#c4
Issues like that are bogus and https://github.com/google/oss-fuzz/pull/7401
should fix them. Since it's a &quo
Comment #3 on issue 45636 by evv...@gmail.com: elfutils:fuzz-libdwfl: Crash in
read_long_names
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45636#c3
It seems to be a duplicate of
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45628. Any idea why
OSS-Fuzz keeps reporting it
Comment #2 on issue 45705 by da...@adalogics.com: elfutils:fuzz-libdwfl:
Indirect-leak in __libelf_next_arhdr_wrlock
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45705#c2
(No comment was entered for this change.)
Attachments:
clusterfuzz-testcase-minimized-fuzz-libdwfl
Comment #1 on issue 45705 by da...@adalogics.com: elfutils:fuzz-libdwfl:
Indirect-leak in __libelf_next_arhdr_wrlock
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45705#c1
ASAN report
Running:
/mnt/scratch0/clusterfuzz/bot/inputs/fuzzer-testcases/leak
Comment #2 on issue 45682 by da...@adalogics.com: elfutils:fuzz-libelf:
Misaligned-address in elf_cvt_Verneed
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45682#c2
(No comment was entered for this change.)
Attachments:
clusterfuzz-testcase-minimized-fuzz-libelf
Comment #1 on issue 45682 by da...@adalogics.com: elfutils:fuzz-libelf:
Misaligned-address in elf_cvt_Verneed
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45682#c1
UBSAN report
Running:
/mnt/scratch0/clusterfuzz/bot/inputs/fuzzer-testcases/crash
Comment #2 on issue 45646 by da...@adalogics.com: elfutils:fuzz-libdwfl:
Misaligned-address in __libdw_image_header
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45646#c2
(No comment was entered for this change.)
Attachments:
clusterfuzz-testcase-minimized-fuzz-libdwfl
Comment #1 on issue 45646 by da...@adalogics.com: elfutils:fuzz-libdwfl:
Misaligned-address in __libdw_image_header
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45646#c1
UBSAN report
Running:
/mnt/scratch0/clusterfuzz/bot/inputs/fuzzer-testcases/crash
Comment #2 on issue 45637 by da...@adalogics.com: elfutils:fuzz-libelf: Timeout
in fuzz-libelf
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45637#c2
(No comment was entered for this change.)
Attachments:
clusterfuzz-testcase-minimized-fuzz-libelf-6393240885002240 684 bytes
Comment #1 on issue 45637 by da...@adalogics.com: elfutils:fuzz-libelf: Timeout
in fuzz-libelf
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45637#c1
ASAN report:
Running:
/mnt/scratch0/clusterfuzz/bot/inputs/fuzzer-testcases/timeout-15f79e70f92567039dd67b7c3a16ad3a180b3a6e
ALARM
Comment #2 on issue 45636 by da...@adalogics.com: elfutils:fuzz-libdwfl: Crash
in read_long_names
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45636#c2
(No comment was entered for this change.)
Attachments:
clusterfuzz-testcase-minimized-fuzz-libdwfl-5787862593830912 8.0 KB
Comment #1 on issue 45636 by da...@adalogics.com: elfutils:fuzz-libdwfl: Crash
in read_long_names
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45636#c1
ASAN report
=
==746==ERROR: AddressSanitizer: unknown-crash on
Comment #2 on issue 45635 by da...@adalogics.com: elfutils:fuzz-libdwfl:
Timeout in fuzz-libdwfl
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45635#c2
(No comment was entered for this change.)
Attachments:
clusterfuzz-testcase-minimized-fuzz-libdwfl-5237809772888064 129
Comment #1 on issue 45635 by da...@adalogics.com: elfutils:fuzz-libdwfl:
Timeout in fuzz-libdwfl
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45635#c1
UBSAN report
Running:
/mnt/scratch0/clusterfuzz/bot/inputs/fuzzer-testcases/timeout-2aaefec51e4f82909c4edd9ae287bf51b2eb6dd7
ALARM
Comment #2 on issue 45634 by da...@adalogics.com: elfutils:fuzz-libdwfl:
Misaligned-address in file_read_elf
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45634#c2
(No comment was entered for this change.)
Attachments:
clusterfuzz-testcase-minimized-fuzz-libdwfl
Comment #1 on issue 45634 by da...@adalogics.com: elfutils:fuzz-libdwfl:
Misaligned-address in file_read_elf
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45634#c1
UBSAN report
Running:
/mnt/scratch0/clusterfuzz/bot/inputs/fuzzer-testcases/crash
1 - 100 of 165 matches
Mail list logo
