CVE-2017-2624
published 2018-07-27CVE-2017-2624: It was found that xorg-x11-server before 1.19.0 including uses memcmp() to check the received MIT cookie against a series of valid cookies. If the cookie is…
PriorityP428high7CVSS 3.0
AVLACHPRLUINSUCHIHAH
EPSS
0.67%
48.2th percentile
It was found that xorg-x11-server before 1.19.0 including uses memcmp() to check the received MIT cookie against a series of valid cookies. If the cookie is correct, it is allowed to attach to the Xorg session. Since most memcmp() implementations return after an invalid byte is seen, this causes a time difference between a valid and invalid byte, which could allow an efficient brute force attack.
Affected
10 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | debian_linux | — | — |
| debian | xorg-server | < xorg-server 2:1.19.2-1 (bookworm) | xorg-server 2:1.19.2-1 (bookworm) |
| x.org | x_server | <= 1.19.4 | — |
| x.org | xorg-server | >= 0 < 2:1.19.2-1 | 2:1.19.2-1 |
| x.org | xorg-server | >= 0 < 2:1.19.2-1 | 2:1.19.2-1 |
| x.org | xorg-server | >= 0 < 2:1.19.2-1 | 2:1.19.2-1 |
| x.org | xorg-server | >= 0 < 2:1.19.2-1 | 2:1.19.2-1 |
| x.org | xorg-server | >= 0 < 2:1.15.1-0ubuntu2.9 | 2:1.15.1-0ubuntu2.9 |
| x.org | xorg-server | >= 0 < 2:1.18.4-0ubuntu0.3 | 2:1.18.4-0ubuntu0.3 |
| xorg | xorg-x11-server | — | — |
CVSS provenance
nvdv3.07.0HIGHCVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
nvdv2.01.9LOWAV:L/AC:M/Au:N/C:P/I:N/A:N
osv8.8HIGH
vendor_ubuntu8.8HIGH
vendor_debian5.9LOW
vendor_redhat5.9MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-6pw7-qhf8-rjff: It was found that xorg-x11-server before 1
ghsa_unreviewed·2022-05-13
CVE-2017-2624 [HIGH] CWE-200 GHSA-6pw7-qhf8-rjff: It was found that xorg-x11-server before 1
It was found that xorg-x11-server before 1.19.0 including uses memcmp() to check the received MIT cookie against a series of valid cookies. If the cookie is correct, it is allowed to attach to the Xorg session. Since most memcmp() implementations return after an invalid byte is seen, this causes a time difference between a valid and invalid byte, which could allow an efficient brute force attack.
OSV
CVE-2017-2624: It was found that xorg-x11-server before 1
osv·2018-07-27·CVSS 7.0
CVE-2017-2624 [HIGH] CVE-2017-2624: It was found that xorg-x11-server before 1
It was found that xorg-x11-server before 1.19.0 including uses memcmp() to check the received MIT cookie against a series of valid cookies. If the cookie is correct, it is allowed to attach to the Xorg session. Since most memcmp() implementations return after an invalid byte is seen, this causes a time difference between a valid and invalid byte, which could allow an efficient brute force attack.
OSV
xorg-server, xorg-server-hwe-16.04, xorg-server-lts-xenial vulnerabilities
osv·2017-07-24·CVSS 8.8
CVE-2017-10971 [HIGH] xorg-server, xorg-server-hwe-16.04, xorg-server-lts-xenial vulnerabilities
xorg-server, xorg-server-hwe-16.04, xorg-server-lts-xenial vulnerabilities
It was discovered that the X.Org X server incorrectly handled endianness
conversion of certain X events. An attacker able to connect to an X server,
either locally or remotely, could use this issue to crash the server, or
possibly execute arbitrary code as an administrator. (CVE-2017-10971)
It was discovered that the X.Org X server incorrectly handled endianness
conversion of certain X events. An attacker able to connect to an X server,
either locally or remotely, could use this issue to possibly obtain
sensitive information. (CVE-2017-10972)
Eric Sesterhenn discovered that the X.Org X server incorrectly compared
MIT cookies. An attacker could possibly use this issue to perform a timing
attack and recover the MIT
Ubuntu
X.Org X server vulnerabilities
vendor_ubuntu·2017-07-24·CVSS 8.8
CVE-2017-10971 [HIGH] X.Org X server vulnerabilities
Title: X.Org X server vulnerabilities
Summary: Several security issues were fixed in the X.Org X server.
It was discovered that the X.Org X server incorrectly handled endianness
conversion of certain X events. An attacker able to connect to an X server,
either locally or remotely, could use this issue to crash the server, or
possibly execute arbitrary code as an administrator. (CVE-2017-10971)
It was discovered that the X.Org X server incorrectly handled endianness
conversion of certain X events. An attacker able to connect to an X server,
either locally or remotely, could use this issue to possibly obtain
sensitive information. (CVE-2017-10972)
Eric Sesterhenn discovered that the X.Org X server incorrectly compared
MIT cookies. An attacker could possibly use this issue to perform a ti
Red Hat
xorg-x11-server: timing attack against MIT Cookie
vendor_redhat·2017-02-28·CVSS 5.9
CVE-2017-2624 [MEDIUM] CWE-385 xorg-x11-server: timing attack against MIT Cookie
xorg-x11-server: timing attack against MIT Cookie
It was found that xorg-x11-server before 1.19.0 including uses memcmp() to check the received MIT cookie against a series of valid cookies. If the cookie is correct, it is allowed to attach to the Xorg session. Since most memcmp() implementations return after an invalid byte is seen, this causes a time difference between a valid and invalid byte, which could allow an efficient brute force attack.
Statement: Red Hat Product Security has rated this issue as having Low security
impact. This issue is not currently planned to be addressed in future
updates. For additional information, refer to the Issue Severity
Classification: https://access.redhat.com/security/updates/classification/.
Package: xorg-x11-server (Red Hat Enterprise Linux 5) -
Debian
CVE-2017-2624: xorg-server - It was found that xorg-x11-server before 1.19.0 including uses memcmp() to check...
vendor_debian·2017·CVSS 5.9
CVE-2017-2624 [MEDIUM] CVE-2017-2624: xorg-server - It was found that xorg-x11-server before 1.19.0 including uses memcmp() to check...
It was found that xorg-x11-server before 1.19.0 including uses memcmp() to check the received MIT cookie against a series of valid cookies. If the cookie is correct, it is allowed to attach to the Xorg session. Since most memcmp() implementations return after an invalid byte is seen, this causes a time difference between a valid and invalid byte, which could allow an efficient brute force attack.
Scope: local
bookworm: resolved (fixed in 2:1.19.2-1)
bullseye: resolved (fixed in 2:1.19.2-1)
forky: resolved (fixed in 2:1.19.2-1)
sid: resolved (fixed in 2:1.19.2-1)
trixie: resolved (fixed in 2:1.19.2-1)
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2017-2624 xorg-x11-server: timing attack against MIT Cookie [fedora-all]
bugzilla·2017-02-28·CVSS 5.9
CVE-2017-2624 [MEDIUM] CVE-2017-2624 xorg-x11-server: timing attack against MIT Cookie [fedora-all]
CVE-2017-2624 xorg-x11-server: timing attack against MIT Cookie [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions of F
Bugzilla
CVE-2017-2624 xorg-x11-server: timing attack against MIT Cookie
bugzilla·2017-02-20·CVSS 5.9
CVE-2017-2624 [MEDIUM] CVE-2017-2624 xorg-x11-server: timing attack against MIT Cookie
CVE-2017-2624 xorg-x11-server: timing attack against MIT Cookie
The following flaw was reported in the Xorg server:
Summary and Impact
xorg-server/xorg-server-1.19.0/os/mitauth.c:79 uses memcmp() to check
the received MIT cookie against a series of valid cookies. If the cookie
is correct, it is allowed to attach to the Xorg session. Since most
memcmp() implementations return after an invalid
byte is seen, this causes a time difference between a valid and invalid
byte, which in theory could allow an efficient brute force attack[1].
Analysis
X41 was not able to measure a significant difference using the optimized
memcmp() version of a standard Linux system, but for a naive implementation
consisting of a loop comparing the bytes. Since timing attacks against
memcmp() have been successful i
http://www.securityfocus.com/bid/96480http://www.securitytracker.com/id/1037919https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2624https://gitlab.freedesktop.org/xorg/xserver/commit/d7ac755f0b618eb1259d93c8a16ec6e39a18627chttps://lists.debian.org/debian-lts-announce/2017/11/msg00032.htmlhttps://security.gentoo.org/glsa/201704-03https://security.gentoo.org/glsa/201710-30https://www.x41-dsec.de/lab/advisories/x41-2017-001-xorg/http://www.securityfocus.com/bid/96480http://www.securitytracker.com/id/1037919https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2624https://gitlab.freedesktop.org/xorg/xserver/commit/d7ac755f0b618eb1259d93c8a16ec6e39a18627chttps://lists.debian.org/debian-lts-announce/2017/11/msg00032.htmlhttps://security.gentoo.org/glsa/201704-03https://security.gentoo.org/glsa/201710-30https://www.x41-dsec.de/lab/advisories/x41-2017-001-xorg/
2018-07-27
Published