From: Mark Wielaard <mark@klomp.org>
To: Evgeny Vereshchagin <evvers@ya.ru>
Cc: elfutils-devel@sourceware.org
Subject: Re: OSS-Fuzz issue 42877
Date: Fri, 24 Dec 2021 02:23:06 +0100 [thread overview]
Message-ID: <YcUg+thbkjK7QvJ2@wildebeest.org> (raw)
In-Reply-To: <6E8C30A5-04FE-498A-9BA8-5484134B2629@ya.ru>
Hi Evgeny,
On Fri, Dec 24, 2021 at 12:49:53AM +0300, Evgeny Vereshchagin wrote:
> All those issues can be reproduced by downloading public testcases and
> passing them to ./fuzz/dwfl-core. That particular issue can be reproduced with
> ```
> autoreconf -i -f
> ./configure --enable-maintainer-mode --enable-sanitize-address --enable-sanitize-undefined
> make -j$(nproc) V=1
> make -C tests fuzz-dwfl-core
>
> wget -O CRASH https://oss-fuzz.com/download?testcase_id=4756614962348032
>
> LD_LIBRARY_PATH="./libdw;./libelf" ./tests/fuzz-dwfl-core ./CRASH
> Running: ./CRASH
> =================================================================
> ==266852==ERROR: AddressSanitizer: unknown-crash on address 0x7f492ff9c000 at pc 0x7f4934340b00 bp 0x7ffc09558f30 sp 0x7ffc095586e0
> READ of size 64 at 0x7f492ff9c000 thread T0
> #0 0x7f4934340aff in __interceptor_memcpy (/lib64/libasan.so.6+0x39aff)
> #1 0x7f4933f2aa90 in memcpy /usr/include/bits/string_fortified.h:29
> #2 0x7f4933f2aa90 in dwfl_segment_report_module /home/vagrant/elfutils/libdwfl/dwfl_segment_report_module.c:385
Thanks that is useful. I think this issue has the same root cause as
an issue found by afl-fuzz for which I posted a patch here:
https://sourceware.org/pipermail/elfutils-devel/2021q4/004597.html
Cheers,
Mark
prev parent reply other threads:[~2021-12-24 1:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-23 21:49 Evgeny Vereshchagin
2021-12-24 1:23 ` Mark Wielaard [this message]
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=YcUg+thbkjK7QvJ2@wildebeest.org \
--to=mark@klomp.org \
--cc=elfutils-devel@sourceware.org \
--cc=evvers@ya.ru \
/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).