CVE-2017-2624

What it is

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.

At a glance

Exploitability

Can be exploited locally on the machine without logging in. High risk of data exposure.

Exploit odds

0.7% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2018-07-27 18:29 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 01:16 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.7% in the next 30 days (EPSS).
• Severity: 5.9 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2018-07-27 18:29 UTC

Last modified

2026-06-17 01:16 UTC

Exploit probability

0.7% · EPSS, next 30 days

Weakness

CWE-385

Record status

Modified

Affected

• x.org X Server ≤ 1.19.4
• Debian Linux 7.0

Attack profile CVSS 3.0 · 5.9

Attack vector

Local

Complexity

High

Privileges needed

None

User interaction

None

Scope

Changed

Confidentiality

High

Integrity

None

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2017-2624.md and follow it. Check whether this project is affected by CVE-2017-2624. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge