It was discovered that OpenSSH client did not correctly handle situations when untrusted X11 forwarding was requested and generation of the untrusted authentication cookie failed. The ssh client continued by generating fake authentication cookie and allowed remote X clients to connect the local X server. The decision if client connection was accepted was delegated to the X server which, depending on its configuration, could allow clients to open trusted X connection. This would lead to remote X clients having more privileged access to the local X server than intended. This problem can occur when X server does not include or enable X Security extension (for X.org X server, this extension is not compiled in by default since 2007) and when it has authentication methods besides MIT cookies enabled (e.g. localuser authentication allowing all X connections from a local user who owns the X session). Both of these conditions are satisfied on Red Hat Enterprise Linux 7 and current Fedora versions. The X server does not have X Security extension compiled in and 'xhost +si:localuser:`id -un`' is run from the xinit scripts. Therefore remote X clients are granted trusted access to the local X server when 'ssh -X' is used, as if 'ssh -Y' was actually used. The X server on Red Hat Enterprise Linux 6 includes X Security extension (as of RHSA-2013:1620 - http://rhn.redhat.com/errata/RHSA-2013-1620.html - which was released as part of Red Hat Enterprise Linux 6.5) and hence does not fall back to the use of fake authentication cookie. This issue was corrected upstream in version 7.1p2: http://www.openssh.com/txt/release-7.1p2 Upstream commit: https://anongit.mindrot.org/openssh.git/commit/?id=ed4ce82dbfa8a3a3c8ea6fa0db113c71e234416c which needs to be applied after: https://anongit.mindrot.org/openssh.git/commit/?id=f98a09cacff7baad8748c9aa217afd155a4d493f
This issue was originally reported upstream in Oct 2015 and the fix was waiting for inclusion in the next OpenSSH upstream release.
Actually, openssh-7.1p2 does not fix this issue and it will be as part of the next release. There was a bug in release notes: http://lists.mindrot.org/pipermail/openssh-unix-dev/2016-January/034684.html
Thank you for pointing that error out!
Created openssh tracking bugs for this issue: Affects: fedora-all [bug 1298840]
Created gsi-openssh tracking bugs for this issue: Affects: fedora-all [bug 1298841] Affects: epel-all [bug 1298842]
CVE-2016-1908 was assigned to this issue: http://seclists.org/oss-sec/2016/q1/115
gsi-openssh-7.1p2-3.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
(In reply to Jakub Jelen from comment #4) > Actually, openssh-7.1p2 does not fix this issue and it will be as part of > the next release. This issue was fixed in 7.2: http://www.openssh.com/txt/release-7.2
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
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