Bug 1435646 (CVE-2017-6966)

Summary: CVE-2017-6966 binutils: Use-after-free in target_specific_reloc_handling in readelf
Product: [Other] Security Response Reporter: Adam Mariš <amaris>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: erik-fedora, fedora-mingw, jakub, klember, nickc, ohudlick, rjones, sardella, yozone, yselkowi
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
A vulnerability was found in readelf; part of binutils. A crafted executable or shared library could cause use-after-free and out-of-bounds writes, leading to a crash or possible code execution.
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-10-21 11:52:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1435307, 1435308, 1435309    
Bug Blocks: 1435650    

Description Adam Mariš 2017-03-24 12:41:30 UTC
readelf in GNU Binutils 2.28 has a use-after-free (specifically read-after-free) error while processing multiple, relocated sections in an MSP430 binary. This is caused by mishandling of an invalid symbol index, and mishandling of state across invocations.

Upstream bug:

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

Upstream patch:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=f84ce13b6708801ca1d6289b7c4003e2f5a6d7f9

Comment 1 Adam Mariš 2017-03-24 12:58:36 UTC
Created mingw-binutils tracking bugs for this issue:

Affects: epel-all [bug 1435309]

Comment 4 Doran Moppert 2017-05-30 04:42:17 UTC
Statement:

Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.