From: "da… via monorail" <monorail+v2.1355924921@chromium.org>
To: elfutils-devel@sourceware.org
Subject: Issue 45628 in oss-fuzz: elfutils:fuzz-libdwfl: Heap-buffer-overflow in strtol
Date: Thu, 17 Mar 2022 07:33:43 -0700 [thread overview]
Message-ID: <000000000000bc922b05da6aead3@google.com> (raw)
In-Reply-To: <0=71cc74a7ba1af446b7ed6b9a08b414d9=f5a9375df2c55c28bce4b7cdfdfda2ef=oss-fuzz@monorail-prod.appspotmail.com>
Comment #2 on issue 45628 by da...@adalogics.com: elfutils:fuzz-libdwfl: Heap-buffer-overflow in strtol
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45628#c2
Stack trace from detailed report:
==2680==ERROR: AddressSanitizer: unknown-crash on address 0x7fd79225d000 at pc 0x00000044fd53 bp 0x7ffd96c8ead0 sp 0x7ffd96c8e288
READ of size 249 at 0x7fd79225d000 thread T0
SCARINESS: 16 (multi-byte-read-unknown-crash)
#0 0x44fd52 in StrtolFixAndCheck(void*, char const*, char**, char*, int) /src/llvm-project/compiler-rt/lib/sanitizer_common/sanitizer_common_interceptors.inc:3440:3
#1 0x488f30 in strtol /src/llvm-project/compiler-rt/lib/asan/asan_interceptors.cpp:484:3
#2 0x5a4f1b in atol /usr/include/stdlib.h:368:10
#3 0x5a4f1b in read_long_names /src/elfutils/libelf/elf_begin.c:766:13
#4 0x5a4f1b in __libelf_next_arhdr_wrlock /src/elfutils/libelf/elf_begin.c:912:8
#5 0x5a65c2 in dup_elf /src/elfutils/libelf/elf_begin.c:1061:10
#6 0x5a65c2 in lock_dup_elf /src/elfutils/libelf/elf_begin.c:1119:10
#7 0x5a65c2 in elf_begin /src/elfutils/libelf/elf_begin.c:1165:11
#8 0x4e3732 in process_archive /src/elfutils/libdwfl/offline.c:251:17
#9 0x4e3732 in process_file /src/elfutils/libdwfl/offline.c:125:14
#10 0x4e4136 in __libdwfl_report_offline /src/elfutils/libdwfl/offline.c:287:22
#11 0x4e4136 in dwfl_report_offline /src/elfutils/libdwfl/offline.c:316:10
#12 0x4e120d in LLVMFuzzerTestOneInput /src/fuzz-libdwfl.c:47:22
#13 0x4d732b in main
#14 0x7fd7930a70b2 in __libc_start_main /build/glibc-eX1tMB/glibc-2.31/csu/libc-start.c:308:16
#15 0x41d65d in _start
--
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-17 14:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0=71cc74a7ba1af446b7ed6b9a08b414d9=f5a9375df2c55c28bce4b7cdfdfda2ef=oss-fuzz@monorail-prod.appspotmail.com>
2022-03-17 5:20 ` ClusterFuzz-External via monorail
2022-03-17 14:31 ` da… via monorail
2022-03-17 14:33 ` da… via monorail [this message]
2022-03-18 11:47 ` evv… via monorail
2022-03-20 4:28 ` evv… via monorail
2022-03-22 14:16 ` 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=000000000000bc922b05da6aead3@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).