CVE-2018-8584 json
An elevation of privilege vulnerability exists when Windows improperly handles calls to Advanced Local Procedure Call (ALPC), aka "Windows…
published 7y ago modified 4mo ago also EUVD-2018-20200
- cvss
- 7.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.7%
- EPSS 2.7% chance of exploitation in 30 days, percentile 86%
- public exploits
- 1
- Exploit-DB
Summary
An elevation of privilege vulnerability exists when Windows improperly handles calls to Advanced Local Procedure Call (ALPC), aka "Windows ALPC Elevation of Privilege Vulnerability." This affects Windows Server 2016, Windows 10, Windows Server 2019, Windows 10 Servers.
Patch / fix
Is CVE-2018-8584 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- Published
- First public exploit (EDB-46104)
Exploit prediction
2.70% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-46104 Microsoft Windows - DSSVC CheckFilePermission Arbitrary File Deletion local, 2019-01-09
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.8 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
Affected products
- Microsoft Windows Server 2016
- Microsoft Windows 10
- Microsoft Windows Server 2019
- Microsoft Windows 10 Servers
Classification
- Weakness
-
- CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition
References
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2018-8584
patch, vendor-advisory
-
exploit-db.com
/exploits/46104/
exploit, third-party-advisory, vdb-entry
-
securitytracker.com
/id/1042119
vdb-entry, third-party-advisory
-
securityfocus.com
/bid/105808
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2018-8584
- NVD CVE-2018-8584
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.