Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1469657 - (CVE-2017-9755) CVE-2017-9755 binutils: Global buffer over-read in opcodes/i386-dis.c while checking invalid registers
CVE-2017-9755 binutils: Global buffer over-read in opcodes/i386-dis.c while c...
Status: CLOSED WONTFIX
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20170711,reported=2...
: Security
Depends On: 1469658 1469659
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-11 11:12 EDT by Pedro Sampaio
Modified: 2017-07-12 10:34 EDT (History)
14 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-07-11 11:22:52 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Pedro Sampaio 2017-07-11 11:12:09 EDT
opcodes/i386-dis.c in GNU Binutils 2.28 does not consider the number of registers for bnd mode, which allows attackers to cause a denial of service (application crash) or possibly have unspecified other impact via a crafted binary file, as demonstrated by mishandling of this file during "objdump -D" execution.

Upstream bug:

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

Upstream patch:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=0d96e4df4812c3bad77c229dfef47a9bc115ac12
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=8cac017d35ef374e65acc98818a17cf8a652cbd0

References:
Comment 1 Pedro Sampaio 2017-07-11 11:12:41 EDT
Created binutils tracking bugs for this issue:

Affects: fedora-all [bug 1469658]


Created mingw-binutils tracking bugs for this issue:

Affects: epel-all [bug 1469659]

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