From: Mark Wielaard <mark@klomp.org>
To: Evgeny Vereshchagin <evvers@ya.ru>
Cc: elfutils-devel@sourceware.org,
ClusterFuzz-External via monorail
<monorail+v2.382749006@chromium.org>
Subject: Re: Issue 60887 in oss-fuzz: elfutils:fuzz-libelf: Direct-leak in __libelf_decompress_zlib
Date: Sat, 29 Jul 2023 16:38:05 +0200 [thread overview]
Message-ID: <20230729143805.GF28605@gnu.wildebeest.org> (raw)
In-Reply-To: <0000000000008b5d4706017e070e@google.com>
Hi Evgeny,
Do you happen to know what clusterfuzz is trying to tell us? The
stack trace is not detailed enough to understand what is going on.
The reproducer is a corrupt ELF file with no indication of what code
is being run on it. And the detailed report is not accessible (it
seems to require a google or github account to login).
Thanks,
Mark
On Thu, Jul 27, 2023 at 01:44:24PM -0700, ClusterFuzz-External via monorail via Elfutils-devel wrote:
> Status: New
> Owner: ----
> CC: elfut...@sourceware.org, da...@adalogics.com, evv...@gmail.com, izzeem@google.com
> Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Stability-Memory-LeakSanitizer Engine-libfuzzer OS-Linux Proj-elfutils Reported-2023-07-27
> Type: Bug
>
> New issue 60887 by ClusterFuzz-External: elfutils:fuzz-libelf: Direct-leak in __libelf_decompress_zlib
> https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=60887
>
> Detailed Report: https://oss-fuzz.com/testcase?key=4651173658099712
>
> Project: elfutils
> Fuzzing Engine: libFuzzer
> Fuzz Target: fuzz-libelf
> Job Type: libfuzzer_asan_elfutils
> Platform Id: linux
>
> Crash Type: Direct-leak
> Crash Address:
> Crash State:
> __libelf_decompress_zlib
> __libelf_decompress_elf
> get_zdata
>
> Sanitizer: address (ASAN)
>
> Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_elfutils&range=202203161800:202203170000
>
> Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4651173658099712
>
> 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.
next prev parent reply other threads:[~2023-07-29 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0=71cc74a7ba1af446b7ed6b9a08b414d9=179906139b10d40134117f89b865bd88=oss-fuzz@monorail-prod.appspotmail.com>
2023-07-27 20:44 ` ClusterFuzz-External via monorail
2023-07-29 14:38 ` Mark Wielaard [this message]
2023-07-29 22:00 ` evv… via monorail
2023-07-30 12:03 ` Mark Wielaard
2023-08-03 18:08 ` 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=20230729143805.GF28605@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=elfutils-devel@sourceware.org \
--cc=evvers@ya.ru \
--cc=monorail+v2.382749006@chromium.org \
/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).