* Issue 45636 in oss-fuzz: elfutils:fuzz-libdwfl: Crash in read_long_names
[not found] <0=71cc74a7ba1af446b7ed6b9a08b414d9=ab8031fc7889ffb2d47f2ef4275a0985=oss-fuzz@monorail-prod.appspotmail.com>
@ 2022-03-17 7:01 ` ClusterFuzz-External via monorail
2022-03-20 10:01 ` da… via monorail
` (3 subsequent siblings)
4 siblings, 0 replies; 5+ messages in thread
From: ClusterFuzz-External via monorail @ 2022-03-17 7:01 UTC (permalink / raw)
To: elfutils-devel
Status: New
Owner: ----
CC: elfut...@sourceware.org, da...@adalogics.com, evv...@gmail.com, izzeem@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 issue 45636 by ClusterFuzz-External: elfutils:fuzz-libdwfl: Crash in read_long_names
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45636
Detailed Report: https://oss-fuzz.com/testcase?key=5787862593830912
Project: elfutils
Fuzzing Engine: afl
Fuzz Target: fuzz-libdwfl
Job Type: afl_asan_elfutils
Platform Id: linux
Crash Type: UNKNOWN
Crash Address: 0x7fdae5ef5000
Crash State:
read_long_names
__libelf_next_arhdr_wrlock
dup_elf
Sanitizer: address (ASAN)
Recommended Security Severity: Medium
Regressed: https://oss-fuzz.com/revisions?job=afl_asan_elfutils&range=202203161800:202203170000
Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5787862593830912
Issue filed automatically.
See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally.
When you fix this bug, please
* mention the fix revision(s).
* state whether the bug was a short-lived regression or an old bug in any stable releases.
* add any other useful information.
This information can help downstream consumers.
If you need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored.
--
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 add a comment.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Issue 45636 in oss-fuzz: elfutils:fuzz-libdwfl: Crash in read_long_names
[not found] <0=71cc74a7ba1af446b7ed6b9a08b414d9=ab8031fc7889ffb2d47f2ef4275a0985=oss-fuzz@monorail-prod.appspotmail.com>
2022-03-17 7:01 ` Issue 45636 in oss-fuzz: elfutils:fuzz-libdwfl: Crash in read_long_names ClusterFuzz-External via monorail
@ 2022-03-20 10:01 ` da… via monorail
2022-03-20 10:02 ` da… via monorail
` (2 subsequent siblings)
4 siblings, 0 replies; 5+ messages in thread
From: da… via monorail @ 2022-03-20 10:01 UTC (permalink / raw)
To: elfutils-devel
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 0x7f1a9af3d000 at pc 0x00000048a379 bp 0x7ffeb1d3c230 sp 0x7ffeb1d3b9e8
READ of size 985 at 0x7f1a9af3d000 thread T0
SCARINESS: 16 (multi-byte-read-unknown-crash)
#0 0x48a378 in __interceptor_atol /src/llvm-project/compiler-rt/lib/asan/asan_interceptors.cpp:522:3
#1 0x5b4615 in read_long_names /src/elfutils/libelf/elf_begin.c:766:13
#2 0x5b2aa4 in __libelf_next_arhdr_wrlock /src/elfutils/libelf/elf_begin.c:912:8
#3 0x5b6d7d in dup_elf /src/elfutils/libelf/elf_begin.c:1061:10
#4 0x5b5028 in lock_dup_elf /src/elfutils/libelf/elf_begin.c:1119:10
#5 0x5b4e36 in elf_begin /src/elfutils/libelf/elf_begin.c:0
#6 0x4db735 in process_archive /src/elfutils/libdwfl/offline.c:251:17
#7 0x4db181 in process_file /src/elfutils/libdwfl/offline.c:125:14
#8 0x4daf3b in __libdwfl_report_offline /src/elfutils/libdwfl/offline.c:287:22
#9 0x4db2a2 in dwfl_report_offline /src/elfutils/libdwfl/offline.c:316:10
#10 0x4d842f in LLVMFuzzerTestOneInput /src/fuzz-libdwfl.c:47:22
#11 0x4d8225 in ExecuteFilesOnyByOne aflplusplus/utils/aflpp_driver/aflpp_driver.c:191:7
#12 0x4d8095 in main aflplusplus/utils/aflpp_driver/aflpp_driver.c:0
#13 0x7f1a9bd060b2 in __libc_start_main /build/glibc-eX1tMB/glibc-2.31/csu/libc-start.c:308:16
#14 0x41e58d in _start
Address 0x7f1a9af3d000 is a wild pointer inside of access range of size 0x0000000003d9.
SUMMARY: AddressSanitizer: unknown-crash (/mnt/scratch0/clusterfuzz/bot/builds/clusterfuzz-builds-afl_elfutils_b7ca3a6bcc40cef461446d759ca780e6ea3657cd/revisions/fuzz-libdwfl+0x48a378)
Shadow bytes around the buggy address:
0x0fe3d35df9b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0fe3d35df9c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0fe3d35df9d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0fe3d35df9e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0fe3d35df9f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
=>0x0fe3d35dfa00:[fe]fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe
0x0fe3d35dfa10: fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe
0x0fe3d35dfa20: fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe
0x0fe3d35dfa30: fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe
0x0fe3d35dfa40: fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe
0x0fe3d35dfa50: fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe fe
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
==746==ABORTING
--
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 add a comment.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Issue 45636 in oss-fuzz: elfutils:fuzz-libdwfl: Crash in read_long_names
[not found] <0=71cc74a7ba1af446b7ed6b9a08b414d9=ab8031fc7889ffb2d47f2ef4275a0985=oss-fuzz@monorail-prod.appspotmail.com>
2022-03-17 7:01 ` Issue 45636 in oss-fuzz: elfutils:fuzz-libdwfl: Crash in read_long_names ClusterFuzz-External via monorail
2022-03-20 10:01 ` da… via monorail
@ 2022-03-20 10:02 ` da… via monorail
2022-03-21 0:54 ` evv… via monorail
2022-03-22 14:41 ` ClusterFuzz-External via monorail
4 siblings, 0 replies; 5+ messages in thread
From: da… via monorail @ 2022-03-20 10:02 UTC (permalink / raw)
To: elfutils-devel
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
--
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 add a comment.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Issue 45636 in oss-fuzz: elfutils:fuzz-libdwfl: Crash in read_long_names
[not found] <0=71cc74a7ba1af446b7ed6b9a08b414d9=ab8031fc7889ffb2d47f2ef4275a0985=oss-fuzz@monorail-prod.appspotmail.com>
` (2 preceding siblings ...)
2022-03-20 10:02 ` da… via monorail
@ 2022-03-21 0:54 ` evv… via monorail
2022-03-22 14:41 ` ClusterFuzz-External via monorail
4 siblings, 0 replies; 5+ messages in thread
From: evv… via monorail @ 2022-03-21 0:54 UTC (permalink / raw)
To: elfutils-devel
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?
It can't be reproduced with libfuzzer either: https://github.com/google/oss-fuzz/pull/7403
--
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 add a comment.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Issue 45636 in oss-fuzz: elfutils:fuzz-libdwfl: Crash in read_long_names
[not found] <0=71cc74a7ba1af446b7ed6b9a08b414d9=ab8031fc7889ffb2d47f2ef4275a0985=oss-fuzz@monorail-prod.appspotmail.com>
` (3 preceding siblings ...)
2022-03-21 0:54 ` evv… via monorail
@ 2022-03-22 14:41 ` ClusterFuzz-External via monorail
4 siblings, 0 replies; 5+ messages in thread
From: ClusterFuzz-External via monorail @ 2022-03-22 14:41 UTC (permalink / raw)
To: elfutils-devel
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 https://oss-fuzz.com/revisions?job=afl_asan_elfutils&range=202203210605:202203211200
If this is incorrect, please file a bug on https://github.com/google/oss-fuzz/issues/new
--
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 add a comment.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2022-03-22 14:41 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <0=71cc74a7ba1af446b7ed6b9a08b414d9=ab8031fc7889ffb2d47f2ef4275a0985=oss-fuzz@monorail-prod.appspotmail.com>
2022-03-17 7:01 ` Issue 45636 in oss-fuzz: elfutils:fuzz-libdwfl: Crash in read_long_names ClusterFuzz-External via monorail
2022-03-20 10:01 ` da… via monorail
2022-03-20 10:02 ` da… via monorail
2022-03-21 0:54 ` evv… via monorail
2022-03-22 14:41 ` ClusterFuzz-External via monorail
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).