Bug 1316829 (CVE-2016-3115) - CVE-2016-3115 openssh: missing sanitisation of input for X11 forwarding
Summary: CVE-2016-3115 openssh: missing sanitisation of input for X11 forwarding
Status: CLOSED ERRATA
Alias: CVE-2016-3115
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard: impact=moderate,public=20160310,repor...
Keywords: Security
Depends On: 1316830 1317816 1317817 1317818 1317819 1318201 1318202
Blocks: 1316832
TreeView+ depends on / blocked
 
Reported: 2016-03-11 09:11 UTC by Andrej Nemec
Modified: 2016-08-31 14:17 UTC (History)
11 users (show)

(edit)
It was discovered that the OpenSSH server did not sanitize data received in requests to enable X11 forwarding. An authenticated client with restricted SSH access could possibly use this flaw to bypass intended restrictions.
Clone Of:
(edit)
Last Closed: 2016-03-21 21:03:14 UTC


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:0465 normal SHIPPED_LIVE Moderate: openssh security update 2016-03-22 00:44:52 UTC
Red Hat Product Errata RHSA-2016:0466 normal SHIPPED_LIVE Moderate: openssh security update 2016-03-22 00:18:13 UTC

Description Andrej Nemec 2016-03-11 09:11:18 UTC
Missing sanitisation of untrusted input allows an authenticated user who is able to request X11 forwarding to inject commands to xauth(1).

Injection of xauth commands grants the ability to read arbitrary files under the authenticated user's privilege. Other xauth commands allow limited information leakage, file overwrite, port probing and generally expose xauth(1), which was not written with a hostile user in mind, as an attack surface.

xauth(1) is run under the user's privilege, so this vulnerability offers no additional access to unrestricted accounts, but could circumvent key or account restrictions such as sshd_config ForceCommand, authorized_keys command="..." or restricted shells.

External references:

http://www.openssh.com/txt/x11fwd.adv

CVE assignment:

http://seclists.org/oss-sec/2016/q1/593

Comment 1 Andrej Nemec 2016-03-11 09:11:41 UTC
Created openssh tracking bugs for this issue:

Affects: fedora-all [bug 1316830]

Comment 2 Fedora Update System 2016-03-13 23:53:19 UTC
openssh-7.2p2-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.

Comment 5 Huzaifa S. Sidhpurwala 2016-03-15 10:19:28 UTC
Statement:

(none)

Comment 6 Martin Prpič 2016-03-15 11:36:28 UTC
Mitigation:

Set X11Forwarding=no in sshd_config.

For authorized_keys that specify a "command" restriction, this issue can be mitigated by also setting the "no-X11-forwarding" restriction. In OpenSSH 7.2 and later, the "restrict" restriction can be used instead, which includes the "no-X11-forwarding" restriction.

Comment 9 Tomas Hoger 2016-03-16 09:25:13 UTC
Created gsi-openssh tracking bugs for this issue:

Affects: fedora-all [bug 1318201]
Affects: epel-all [bug 1318202]

Comment 10 errata-xmlrpc 2016-03-21 20:18:36 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 6

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

Comment 11 errata-xmlrpc 2016-03-21 20:45:30 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7

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

Comment 12 Fedora Update System 2016-03-26 18:12:36 UTC
openssh-7.2p2-1.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.

Comment 13 Fedora Update System 2016-03-29 19:19:34 UTC
openssh-6.9p1-11.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.


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