From: Mark Wielaard <mark@klomp.org>
To: oss-fuzz@monorail-prod.appspotmail.com
Cc: elfutils-devel@sourceware.org,
ClusterFuzz-External via monorail
<monorail+v2.382749006@chromium.org>
Subject: Re: Issue 42877 in oss-fuzz: elfutils:fuzz-dwfl-core: Crash in dwfl_segment_report_module
Date: Thu, 23 Dec 2021 19:18:29 +0100 [thread overview]
Message-ID: <YcS9dccpUjqrHZaB@wildebeest.org> (raw)
In-Reply-To: <0000000000007cca9405d3d40701@google.com>
Hi,
On Thu, Dec 23, 2021 at 10:01:35AM -0800, ClusterFuzz-External via monorail via Elfutils-devel wrote:
> Status: New
> Owner: ----
> CC: elfut...@sourceware.org, evv...@gmail.com, izzeem@google.com
> Labels: ClusterFuzz Reproducible Stability-UndefinedBehaviorSanitizer Engine-libfuzzer OS-Linux Security_Severity-Medium Proj-elfutils Reported-2021-12-23
> Type: Bug-Security
>
> New issue 42877 by ClusterFuzz-External: elfutils:fuzz-dwfl-core: Crash in dwfl_segment_report_module
> https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=42877
>
> Detailed Report: https://oss-fuzz.com/testcase?key=4756614962348032
Thanks for the report, but this is not enough information to reproduce
and fix the issue. Please make the detailed reports public so we can
act on this report.
Cheers,
Mark
next prev parent reply other threads:[~2021-12-23 18:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0=71cc74a7ba1af446b7ed6b9a08b414d9=5f9b406fb67d177ccef527f9e4a0fb35=oss-fuzz@monorail-prod.appspotmail.com>
2021-12-23 18:01 ` ClusterFuzz-External via monorail
2021-12-23 18:18 ` Mark Wielaard [this message]
2021-12-23 18:11 ` ClusterFuzz-External via monorail
2022-01-04 16:46 ` 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=YcS9dccpUjqrHZaB@wildebeest.org \
--to=mark@klomp.org \
--cc=elfutils-devel@sourceware.org \
--cc=monorail+v2.382749006@chromium.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).