Bug 1260035 - Specially crafted binary can cause readelf to read from an arbitrary address-
Summary: Specially crafted binary can cause readelf to read from an arbitrary address-
Alias: None
Product: Red Hat Developer Toolset
Classification: Red Hat
Component: binutils
Version: DTS 4.1 RHEL 6
Hardware: All
OS: All
Target Milestone: alpha
: 4.1
Assignee: Nick Clifton
QA Contact: Miloš Prchlík
Depends On: 1260034 1409817
Blocks: 1260158
TreeView+ depends on / blocked
Reported: 2015-09-04 09:30 UTC by Nick Clifton
Modified: 2017-01-03 14:16 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1260034
: 1260158 (view as bug list)
Last Closed: 2016-05-31 08:43:09 UTC
Target Upstream Version:

Attachments (Terms of Use)
Fuzzed binary that triggers readelf bug (5.80 KB, application/octet-stream)
2015-09-04 09:30 UTC, Nick Clifton
no flags Details

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1148 0 normal SHIPPED_LIVE devtoolset-4-binutils bug fix and enhancement update 2016-05-31 12:38:24 UTC
Sourceware 18879 0 None None None Never

Description Nick Clifton 2015-09-04 09:30:25 UTC
Created attachment 1070189 [details]
Fuzzed binary that triggers readelf bug

+++ This bug was initially created as a clone of Bug #1260034 +++

Description of problem:

  Readelf can be fooled into attempting to read from an arbitrary memory location if it is run against a specially crafted binary.

Version-Release number of selected component (if applicable):

  All versions.

How reproducible:

  Run "readelf -a test00-min'

Actual results:


Expected results:

  error message

Additional info:

  The bug has been fixed in the upstream FSF sources.  The patch can be found here:

Comment 1 Nick Clifton 2016-02-04 16:06:28 UTC
binutils-2.25.1-2.el6 contains a fix for this problem.

Comment 3 Miloš Prchlík 2016-03-08 09:00:37 UTC
Verified for build devtoolset-4-binutils-2.25.1-3.el6.

Comment 5 errata-xmlrpc 2016-05-31 08:43:09 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.