From: "leftcopy.chx at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug libelf/25069] AddressSanitizer: heap-buffer-overflow at libdwelf/dwelf_strtab.c:284
Date: Sat, 26 Oct 2019 08:07:00 -0000 [thread overview]
Message-ID: <bug-25069-10460-jAVJb0XEAy@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25069-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25069
--- Comment #3 from leftcopy.chx at gmail dot com ---
Created attachment 12053
--> https://sourceware.org/bugzilla/attachment.cgi?id=12053&action=edit
poc that triggers the crash against git 99dc63b1
Found another poc that triggers this crash. See attachment.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-10-26 8:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-06 16:11 [Bug libelf/25069] New: " leftcopy.chx at gmail dot com
2019-10-26 0:57 ` [Bug libelf/25069] " mark at klomp dot org
2019-10-26 7:31 ` leftcopy.chx at gmail dot com
2019-10-26 8:07 ` leftcopy.chx at gmail dot com [this message]
2019-10-26 20:07 ` mark at klomp dot org
2019-10-26 20:52 ` [Bug tools/25069] " mark at klomp dot org
2019-10-29 14:49 ` mark at klomp dot org
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=bug-25069-10460-jAVJb0XEAy@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@sourceware.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).