CVE-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.
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.69% (FIRST EPSS); higher than 53.6% of all records.
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: xorg-server (Debian:12) 2:1.19.2-1; xorg-server (Debian:7) 2:1.12.4-6+deb7u8; xorg-x11-server (openSUSE:Tumbleweed) 1.20.13-1.2.
Low priority for now. Upgrade to xorg-server (Debian:12) 2:1.19.2-1; xorg-server (Debian:7) 2:1.12.4-6+deb7u8; xorg-x11-server (openSUSE:Tumbleweed) 1.20.13-1.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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
- Jul 27, 2018
- Updated
- Jun 16, 2026
- EPSS
- 0.6% · 53th percentile
- CWE
- CWE-385
Report tools
Action score
28
Low priority for now.
- CVSS
- 28 / 40 · 7.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CNA vs NVD score
- NVD
- 7.0
- CNA · redhat
- 5.9
- 1.1 point gap
CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| x.org | x server | cpe:2.3:a:x.org:x_server |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
Xorg xorg-x11-server
- 1.19.0affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux7.0
- x.org x serverup to 1.19.4 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | xorg-server | before 2:1.19.2-1 | 2:1.19.2-1 |
| Debian:7 | xorg-server | before 2:1.12.4-6+deb7u8 | 2:1.12.4-6+deb7u8 |
| openSUSE:Tumbleweed | xorg-x11-server | before 1.20.13-1.2 | 1.20.13-1.2 |
| SUSE:Linux Enterprise Desktop 12 SP2 | xorg-x11-server | before 7.6_1.18.3-71.1 | 7.6_1.18.3-71.1 |
Same product
x.org: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-6816Xorg-x11-server: heap buffer overflow in devicefocusevent and procxiquerypointer40Plan
- CVE-2018-14665A flaw was found in xorg-x11-server before 1.20.3.40Plan
- CVE-2007-6427The XInput extension in X.Org Xserver before 1.4.1 allows context-dependent attackers to execute arbitrary code via requests related to…38Monitor
Published before and after this one in the same product
- ← EarlierCVE-2017-13721Oct 9, 2017 · In X.Org Server (aka xserver and xorg-server) before 1.19.4, an attacker authenticated to an X server with the X shared memory extension…18Monitor
- ← EarlierCVE-2017-13723Oct 9, 2017 · In X.Org Server (aka xserver and xorg-server) before 1.19.4, a local attacker authenticated to the X server could overflow a global buffer…31Monitor
- Later →CVE-2019-17624Oct 16, 2019 · "" In X.Org X Server 1.20.4, there is a stack-based buffer overflow in the function XQueryKeymap.32Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:xorg-server | 2:1.19.2-1 · Debian:12 | Package registry (OSV) |
| opensuse:xorg-x11-server | 1.20.13-1.2 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:xorg-x11-server | 7.6_1.18.3-71.1 · SUSE:Linux Enterprise Desktop 12 SP2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-385 · Covert Timing ChannelCVSS vector
CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.