CVE-2017-2624
CVE-2017-2624 Vulnerability Analysis & Exploit Intelligence
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.
Published Updated Sources: cvelistV5, redhat
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
1%
chance of exploitation in 30 days
CVSS base
5.9
MEDIUM
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (1)
Products (1)
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 5.9 | CVSS 3.0 | MEDIUM | — | — | cvelistV5 |
Weakness & attack patterns
- CWE-385
References
8 on the record
- security.gentoo.org/glsa/201704-03
vendor-advisory, x_refsource_GENTOO
- gitlab.freedesktop.org/xorg/xserver/commit/d7ac755f0b618eb1259d93c8a16ec6e39a18627c
x_refsource_CONFIRM
- www.securitytracker.com/id/1037919
vdb-entry, x_refsource_SECTRACK
- lists.debian.org/debian-lts-announce/2017/11/msg00032.html
mailing-list, x_refsource_MLIST
- security.gentoo.org/glsa/201710-30
vendor-advisory, x_refsource_GENTOO
- www.securityfocus.com/bid/96480
vdb-entry, x_refsource_BID
- www.x41-dsec.de/lab/advisories/x41-2017-001-xorg/
x_refsource_MISC
- bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2624
x_refsource_CONFIRM
Elsewhere on this site
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.