Bug 1260034

Summary: Specially crafted binary can cause readelf to read from an arbitrary address-
Product: Red Hat Developer Toolset Reporter: Nick Clifton <nickc>
Component: binutilsAssignee: Nick Clifton <nickc>
Status: CLOSED ERRATA QA Contact: Miloš Prchlík <mprchlik>
Severity: low Docs Contact:
Priority: unspecified    
Version: DTS 4.1 RHEL 7CC: law, mcermak, mnewsome, mpolacek, mprchlik, ohudlick
Target Milestone: alpha   
Target Release: 4.1   
Hardware: All   
OS: All   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1260035 1409817 (view as bug list) Environment:
Last Closed: 2016-05-31 08:43:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1260035, 1260158, 1409817    
Description Flags
Fuzzed binary that reproduces the seg-fault when processed with 'readelf -a' none

Description Nick Clifton 2015-09-04 09:28:33 UTC
Created attachment 1070188 [details]
Fuzzed binary that reproduces the seg-fault when processed with 'readelf -a'

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:11 UTC
binutils-2.25.1-2.el7 contains a fix for this problem.

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

Comment 5 errata-xmlrpc 2016-05-31 08:43:00 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.