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.
References
Link | Resource |
---|---|
https://www.x41-dsec.de/lab/advisories/x41-2017-001-xorg/ | Exploit Third Party Advisory |
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2624 | Exploit Issue Tracking Third Party Advisory |
https://security.gentoo.org/glsa/201710-30 | Third Party Advisory |
https://security.gentoo.org/glsa/201704-03 | Third Party Advisory |
https://lists.debian.org/debian-lts-announce/2017/11/msg00032.html | Third Party Advisory |
http://www.securitytracker.com/id/1037919 | Third Party Advisory VDB Entry |
http://www.securityfocus.com/bid/96480 | Third Party Advisory VDB Entry |
https://gitlab.freedesktop.org/xorg/xserver/commit/d7ac755f0b618eb1259d93c8a16ec6e39a18627c | Patch Third Party Advisory |
Information
Published : 2018-07-27 11:29
Updated : 2019-10-09 16:26
NVD link : CVE-2017-2624
Mitre link : CVE-2017-2624
JSON object : View
CWE
CWE-200
Exposure of Sensitive Information to an Unauthorized Actor
Products Affected
debian
- debian_linux
x.org
- xorg-server