Bug 1258802 - (CVE-2015-6806) CVE-2015-6806 screen: Stack overflow due to deep recursion causing process freeze
CVE-2015-6806 screen: Stack overflow due to deep recursion causing process fr...
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=20150807,reported=2...
: Security
Depends On: 1258806
Blocks: 1258805
  Show dependency treegraph
 
Reported: 2015-09-01 06:24 EDT by Adam Mariš
Modified: 2016-11-08 10:50 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-11-04 23:04:12 EST
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 Adam Mariš 2015-09-01 06:24:33 EDT
A vulnerability was found in screen causing stack overflow which results in crashing the screen server process. After running malicious command inside screen, it will recursively call MScrollV to depth n/256. This is time consuming and will overflow the stack if 'n' is huge.

CVE assignment:

http://seclists.org/oss-sec/2015/q3/485

Upstream patch:

http://git.savannah.gnu.org/cgit/screen.git/commit/?id=c336a32a1dcd445e6b83827f83531d4c6414e2cd

Upstream report (contains reproducer):

https://savannah.gnu.org/bugs/?45713
Comment 1 Adam Mariš 2015-09-01 06:28:27 EDT
Created screen tracking bugs for this issue:

Affects: fedora-all [bug 1258806]
Comment 3 Petr Hracek 2015-12-21 04:14:53 EST
Shall I fix the screen bug or close it as WONTFIX too?

Why is this bug closed as WONTFIX?
Comment 4 Adam Mariš 2015-12-21 04:58:45 EST
(In reply to Petr Hracek from comment #3)
> Shall I fix the screen bug or close it as WONTFIX too?
> 
> Why is this bug closed as WONTFIX?

This issue is not planned to be fixed in RHEL due to Low security impact.

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