From: "evv… via monorail" <monorail+v2.2672886254@chromium.org>
To: elfutils-devel@sourceware.org
Subject: Issue 45628 in oss-fuzz: elfutils:fuzz-libdwfl: Heap-buffer-overflow in strtol
Date: Fri, 18 Mar 2022 04:47:35 -0700 [thread overview]
Message-ID: <0000000000007140b705da7cb622@google.com> (raw)
In-Reply-To: <0=71cc74a7ba1af446b7ed6b9a08b414d9=f5a9375df2c55c28bce4b7cdfdfda2ef=oss-fuzz@monorail-prod.appspotmail.com>
Comment #3 on issue 45628 by evv...@gmail.com: elfutils:fuzz-libdwfl: Heap-buffer-overflow in strtol
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45628#c3
> See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally.
FWIW this bug isn't reproducible with libFuzzer and ASan and https://google.github.io/oss-fuzz/advanced-topics/reproducing/#reproducing-bugs seems to be out of date in the sense that it still says that only libFuzzer can be used there. Hopefully I'll fix the documentation once I've gotten round to it.
--
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-18 11:47 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
2022-03-18 11:47 ` evv… via monorail [this message]
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=0000000000007140b705da7cb622@google.com \
--to=monorail+v2.2672886254@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).