From: "da… via monorail" <monorail+v2.1355924921@chromium.org>
To: elfutils-devel@sourceware.org
Subject: Issue 45636 in oss-fuzz: elfutils:fuzz-libdwfl: Crash in read_long_names
Date: Sun, 20 Mar 2022 03:01:47 -0700 [thread overview]
Message-ID: <000000000000c7b88605daa3778a@google.com> (raw)
In-Reply-To: <0=71cc74a7ba1af446b7ed6b9a08b414d9=ab8031fc7889ffb2d47f2ef4275a0985=oss-fuzz@monorail-prod.appspotmail.com>
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.
next prev parent reply other threads:[~2022-03-20 10:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=000000000000c7b88605daa3778a@google.com \
--to=monorail+v2.1355924921@chromium.org \
--cc=elfutils-devel@sourceware.org \
--cc=oss-fuzz@monorail-prod.appspotmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).