Bug 978817 (CVE-2016-4491) - VUL-1: CVE-2016-4491: gcc: Stack overflow due to infinite recursion in d_print_comp
Summary: VUL-1: CVE-2016-4491: gcc: Stack overflow due to infinite recursion in d_prin...
Status: RESOLVED FIXED
Alias: CVE-2016-4491
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents (show other bugs)
Version: unspecified
Hardware: Other Other
: P4 - Low : Normal
Target Milestone: ---
Assignee: Michael Matz
QA Contact: Security Team bot
URL: https://smash.suse.de/issue/168628/
Whiteboard: CVSSv2:SUSE:CVE-2016-4491:4.0:(AV:N/...
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-06 10:14 UTC by Alexander Bergmann
Modified: 2023-02-08 16:51 UTC (History)
2 users (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Bergmann 2016-05-06 10:14:52 UTC 
rh#1333371 / CVE-2016-4491

A vulnerability was found in gcc. A stack overflow in the libiberty demangler library causes its host applications to crash. The stack contains return addresses that are not mapped in the inferior's process address space and/or the stack pointer is pointing to a location outside the default stack region. These conditions likely indicate stack corruption, which is generally considered exploitable.

External references:

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

Proposed patch:

https://gcc.gnu.org/ml/gcc-patches/2016-05/msg00105.html

References:
https://bugzilla.redhat.com/show_bug.cgi?id=1333371
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-4491
http://seclists.org/oss-sec/2016/q2/240
Comment 1 Swamp Workflow Management 2016-05-06 22:01:10 UTC 
bugbot adjusting priority
Comment 2 Sebastian Krahmer 2016-05-09 12:14:31 UTC 
Bug in the name demangler -> VUL-1.
Comment 3 Michael Matz 2023-02-08 16:51:15 UTC 
Fixed since a long time.  (when libiberty, and hence binutils was affected: by version updates to binutils for sle-12 and sle-15 and sle-11 wontfix)