RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1409817 - 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-
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: binutils
Version: 6.9
Hardware: All
OS: All
unspecified
low
Target Milestone: rc
: ---
Assignee: Nick Clifton
QA Contact: Miloš Prchlík
URL:
Whiteboard:
Depends On: 1260034
Blocks: 1260035 1260158
TreeView+ depends on / blocked
 
Reported: 2017-01-03 14:16 UTC by Miloš Prchlík
Modified: 2017-03-21 10:32 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: The readelf program assumed that it has been given a valid ELF input file to examine, and it did not check that this assumption was correct. Consequence: Passing a specially crafted, corrupt ELF file to readelf could cause it to attempt to read from address 0, resulting in readelf being terminated with a seg-fault error. Fix: Patch the readelf sources to add checks on the validity of the ELF section headers. Result: Readelf runs correctly, does not seg-fault and is able to display information on the corrupt input file.
Clone Of: 1260034
Environment:
Last Closed: 2017-03-21 10:32:15 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0677 0 normal SHIPPED_LIVE binutils bug fix update 2017-03-21 12:36:14 UTC
Sourceware 18879 0 None None None 2019-01-04 12:08:57 UTC

Comment 2 Nick Clifton 2017-01-05 11:16:20 UTC 
I have checked in an alternative patch to fix this BZ.

The problem is that the patch for PR 18879 does not work with the RHEL 6.9
binutils sources, since this version of readelf does not actually have the
capability to dump unwind information.  In theory this should mean that the
bug fixed in PR 18879 is never encountered and so no patch is needed.  In
practice however it turns out that the test case for PR 18879 triggers a
*different* bug in the 6.9 binutils, and so a patch is needed after all.
Comment 4 Miloš Prchlík 2017-01-21 18:35:54 UTC 
Verified with build binutils-2.20.51.0.2-5.46.el6.
Comment 6 errata-xmlrpc 2017-03-21 10:32:15 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.

https://rhn.redhat.com/errata/RHBA-2017-0677.html
Note You need to log in before you can comment on or make changes to this bug.