From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug general/22976] global-buffer-overflow in ebl_dynamic_tag_name (libebl/ebldynamictagname.c)
Date: Fri, 16 Mar 2018 18:45:00 -0000 [thread overview]
Message-ID: <bug-22976-10460-IOuGdN20hA@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-22976-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=22976
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2018-03-16
CC| |mark at klomp dot org
Ever confirmed|0 |1
--- Comment #1 from Mark Wielaard <mark at klomp dot org> ---
Thanks. The issue is that there is a new standard SYMTAB_SHNDX which we got
through the new elf.h, but didn't handle in ebldynamictagname.c.
To fix this, and to prevent this from happening in the future I proposed the
following patch:
commit 92581d7eb483cb039e60112b0a03a04c2ffa4df4
Author: Mark Wielaard <mark@klomp.org>
Date: Fri Mar 16 19:42:17 2018 +0100
libebl: Handle SYMTAB_SHNDX in ebl_dynamic_tag_name.
SYMTAB_SHNDX was introduced when elf.h was imported, but not yet handled
in ebl_dynamic_tag_name. Handle it and add an eu_static_assert to make
sure stdtags always contains DT_NUM entries.
https://sourceware.org/bugzilla/show_bug.cgi?id=22976
Signed-off-by: Mark Wielaard <mark@klomp.org>
https://sourceware.org/ml/elfutils-devel/2018-q1/msg00078.html
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2018-03-16 18:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 14:33 [Bug general/22976] New: " probefuzzer at gmail dot com
2018-03-16 18:45 ` mark at klomp dot org [this message]
2018-03-20 21:48 ` [Bug general/22976] " mark at klomp dot org
2018-03-26 12:17 ` 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-22976-10460-IOuGdN20hA@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).