Bug 1473204 - (CVE-2017-10971) CVE-2017-10971 xorg-x11-server: Stack overflow in the endianness conversion of X Events
CVE-2017-10971 xorg-x11-server: Stack overflow in the endianness conversion o...
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20170619,repor...
: Security
Depends On: 1473206
Blocks: 1473208
  Show dependency treegraph
 
Reported: 2017-07-20 04:35 EDT by Andrej Nemec
Modified: 2017-08-16 04:03 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
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 2017-07-20 04:35:59 EDT
In the X.Org X server, a user authenticated to an X Session could crash or execute code in the context of the X Server by exploiting a stack overflow in the endianness conversion of X Events.

Upstream patches:

https://cgit.freedesktop.org/xorg/xserver/commit/?id=215f894965df5fb0bb45b107d84524e700d2073c
https://cgit.freedesktop.org/xorg/xserver/commit/?id=8caed4df36b1f802b4992edcfd282cbeeec35d9d
https://cgit.freedesktop.org/xorg/xserver/commit/?id=ba336b24052122b136486961c82deac76bbde455

References:

https://bugzilla.suse.com/show_bug.cgi?id=1035283
Comment 1 Andrej Nemec 2017-07-20 04:38:39 EDT
Created xorg-x11-server tracking bugs for this issue:

Affects: fedora-all [bug 1473206]
Comment 2 Huzaifa S. Sidhpurwala 2017-08-16 03:17:09 EDT
Since the Xorg server is compiled with Stack-smashing protection, it looks like executing arbitrary code in the context of the X-server (root) involves guessing the stack canary, which can be extremely difficult to pull, hence the maximum impact of this flaw is X-server crash.

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