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
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?
I
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 address
Status: New
Owner:
CC: elfut...@sourceware.org, da...@adalogics.com, evv...@gmail.com,
izz...@google.com
Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible
Stability-AFL OS-Linux Engine-afl Security_Severity-Medium Proj-elfutils
Reported-2022-03-17
Type: Bug-Security
New i