LiveActive security incident?Get immediate response
CVE Record

CVE-2017-2624: It was found that xorg-x11-server before 1.19.0 including uses memcmp() to check the received MIT cookie ag...

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.

MediumCVSS 5.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2017-2624 is a timing weakness in Xorg cookie authentication. On affected systems, a local attacker could infer valid MIT cookie bytes and eventually attach to a user’s Xorg session, risking exposure of session data. The sources do not show confirmed active exploitation.

Executive priority

Treat as a targeted local confidentiality risk, not an internet-wide emergency. Prioritize shared Linux workstations, remote desktop hosts, and administrative jump boxes because compromised X sessions can expose sensitive user activity.

Technical view

Xorg xorg-x11-server used memcmp() to compare received MIT cookies with valid cookies. Because memcmp() commonly exits on the first mismatch, response timing can leak partial correctness and make brute forcing more efficient. CVSS 3.0 is 5.9 with local attack vector, high complexity, no privileges required, changed scope, and high confidentiality impact.

Likely exposure

Exposure is most relevant on Linux or Unix systems running affected Xorg/xorg-server packages, especially multi-user desktop or remote graphical environments where untrusted local users can interact with X authentication.

Exploitation context

The bundled record marks KEV as false and provides no cited evidence of exploitation in the wild. The attack is local and high-complexity, but successful abuse could allow attachment to an Xorg session and confidentiality loss.

Researcher notes

Evidence supports a timing side channel in MIT cookie comparison. The record is older, medium severity, and source data is limited to advisory and upstream references. Do not assume remote exploitability, broader products, or active exploitation without additional evidence.

Mitigation direction

  • Apply vendor security updates for xorg-server or xorg-x11-server packages.
  • Use distribution advisories from Gentoo, Debian, Red Hat, or the relevant OS vendor.
  • Confirm whether upstream commit d7ac755f0b618eb1259d93c8a16ec6e39a18627c is included or backported.
  • Limit untrusted local shell access on graphical systems until patched.
  • Review shared desktop and jump-host systems first.

Validation and detection

  • Inventory installed Xorg or xorg-server package versions across Linux desktops and servers.
  • Check vendor package changelogs for CVE-2017-2624 or the upstream fix commit.
  • Identify systems offering local multi-user access with active Xorg sessions.
  • Verify patched systems still use expected X authentication controls.
  • Document any unsupported systems requiring compensating access restrictions.
Prepared
Confidence
high
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-385: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-2624 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.9 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
7Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.9CVSS 3.0MediumCVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N1.44Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

5.9Medium
CVSS 3.0 vector shape for CVE-2017-2624Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Xorgxorg-x11-server1.19.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-385 · source CWE mapping

Covert Timing Channel

Covert Timing Channel represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.