public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug libdw/23541] heap-buffer-overflow in /elfutils/libdw/dwarf_getaranges.c:156
Date: Sat, 18 Aug 2018 20:50:00 -0000	[thread overview]
Message-ID: <bug-23541-10460-eg7gvtzzbl@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23541-10460@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=23541

Mark Wielaard <mark at klomp dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |FIXED

--- Comment #2 from Mark Wielaard <mark at klomp dot org> ---
commit 29e31978ba51c1051743a503ee325b5ebc03d7e9
Author: Mark Wielaard <mark@klomp.org>
Date:   Sat Aug 18 13:27:48 2018 +0200

    libdw, readelf: Make sure there is enough data to read full aranges header.

    dwarf_getaranges didn't check if there was enough data left to read both
    the address and segment size. readelf didn't check there was enough data
    left to read the segment size.

    https://sourceware.org/bugzilla/show_bug.cgi?id=23541

    Signed-off-by: Mark Wielaard <mark@klomp.org>

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2018-08-18 20:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-17  4:06 [Bug libdw/23541] New: " wcventure at 126 dot com
2018-08-17 19:40 ` [Bug libdw/23541] " mark at klomp dot org
2018-08-18 20:50 ` mark at klomp dot org [this message]
2018-09-03  8:28 ` 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-23541-10460-eg7gvtzzbl@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).