Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1333366 - (CVE-2016-4490) CVE-2016-4490 gcc: Write access violation
CVE-2016-4490 gcc: Write access violation
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=20160401,reported=2...
: Security
Depends On: 1333389 1333388
Blocks: 1333338
  Show dependency treegraph
 
Reported: 2016-05-05 07:45 EDT by Andrej Nemec
Modified: 2017-09-08 08:18 EDT (History)
13 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-08-09 07:38:40 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 Andrej Nemec 2016-05-05 07:45:40 EDT
A vulnerability was found in gcc. Due to the inconsistent use of long and int for string/array length in cp-demangle.c there is an integer overflow that leads to a write access violation. The target crashes on an access violation at an address matching the destination operand of the instruction.

External references:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70498

Upstream patch:

https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=235767
Comment 1 Andrej Nemec 2016-05-05 08:11:25 EDT
Created msp430-gcc tracking bugs for this issue:

Affects: fedora-all [bug 1333388]
Comment 2 Andrej Nemec 2016-05-05 08:11:31 EDT
Created mingw-gcc tracking bugs for this issue:

Affects: epel-all [bug 1333389]
Comment 3 Raphael Sanchez Prudencio 2017-08-09 07:38:54 EDT
Statement:

Red Hat Product Security has rated this issue as having Low 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/.

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