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 1238231 - (CVE-2015-5352) CVE-2015-5352 openssh: XSECURITY restrictions bypass under certain conditions in ssh(1)
CVE-2015-5352 openssh: XSECURITY restrictions bypass under certain conditions...
Status: CLOSED ERRATA
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=20150701,repor...
: Security
Depends On: 1238241 1247864 1281468
Blocks: 1210268 1252864 1278736
  Show dependency treegraph
 
Reported: 2015-07-01 08:42 EDT by Vasyl Kaigorodov
Modified: 2016-05-11 02:45 EDT (History)
16 users (show)

See Also:
Fixed In Version: OpenSSH 6.9
Doc Type: Bug Fix
Doc Text:
It was found that the OpenSSH client did not properly enforce the ForwardX11Timeout setting. A malicious or compromised remote X application could possibly use this flaw to establish a trusted connection to the local X server, even if only untrusted X11 forwarding was requested.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-05-11 02:45:31 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)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:0741 normal SHIPPED_LIVE Moderate: openssh security, bug fix, and enhancement update 2016-05-10 18:29:45 EDT

  None (edit)
Description Vasyl Kaigorodov 2015-07-01 08:42:20 EDT
It was reported that when forwarding X11 connections with ForwardX11Trusted=no, connections made after ForwardX11Timeout expired could be permitted and no longer subject to XSECURITY restrictions because of an ineffective timeout check in ssh(1) coupled with "fail open" behaviour in the X11 server when clients attempted connections with expired credentials. This problem was reported by Jann Horn.

Upstream patches:

http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh/channels.c#rev1.347
http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh/clientloop.c#rev1.274

Portable OpenSSH git commit with both above changes:

https://anongit.mindrot.org/openssh.git/commit/?id=1bf477d3cdf1a864646d59820878783d42357a1d

Upstream release notes:

http://www.openssh.com/txt/release-6.9
Comment 1 Vasyl Kaigorodov 2015-07-01 08:59:11 EDT
Created openssh tracking bugs for this issue:

Affects: fedora-all [bug 1238241]
Comment 2 Fedora Update System 2015-07-10 15:09:17 EDT
openssh-6.6.1p1-13.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 3 Fedora Update System 2015-07-10 15:18:14 EDT
openssh-6.9p1-1.fc22 has been pushed to the Fedora 22 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 6 Tomas Hoger 2015-08-04 03:20:09 EDT
The original reporter published a detailed write-up of this issue.

External References:

https://thejh.net/written-stuff/openssh-6.8-xsecurity
Comment 20 Huzaifa S. Sidhpurwala 2015-10-07 02:53:29 EDT
Statement:

This issue does not affect the version of openssh package as shipped with Red Hat Enterprise Linux 7. This issue affects the version of openssh package as shipped with Red Hat Enterprise Linux 5 and 6.

Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates.
Comment 22 Huzaifa S. Sidhpurwala 2015-12-01 02:24:54 EST
The version of Xserver (xorg-x11-server) shipped with Red Hat Enterprise Linux 7, disables the XSECURITY extension. Hence this flaw does not affect the version of openssh shipped with Red Hat Enterprise Linux 7.

The above also means that there is no way for openssh to do untrusted/restricted forwarding when X server does not have the XC-SECURITY extension.
Comment 25 errata-xmlrpc 2016-05-10 15:28:52 EDT
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 6

Via RHSA-2016:0741 https://rhn.redhat.com/errata/RHSA-2016-0741.html

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