CVE-2018-8410 json
An elevation of privilege vulnerability exists when the Windows Kernel API improperly handles registry objects in memory, aka "Windows Regi…
published 2018-09-13 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-20047
- cvss
- 7.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.0%
- EPSS 4.0% chance of exploitation in 30 days, percentile 90%
- public exploits
- 1
- Exploit-DB
Summary
An elevation of privilege vulnerability exists when the Windows Kernel API improperly handles registry objects in memory, aka "Windows Registry Elevation of Privilege Vulnerability." This affects Windows 7, Windows Server 2012 R2, Windows RT 8.1, Windows Server 2012, Windows 8.1, Windows Server 2016, Windows Server 2008 R2, Windows 10, Windows 10 Servers.
Patch / fix
Timeline
- Published
- First public exploit (EDB-45436)
Exploit prediction
3.98% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-45436 Microsoft Windows - Double Dereference in NtEnumerateKey Elevation of Privilege dos, 2018-09-19
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 7
- Microsoft Windows Server 2012 R2
- Microsoft Windows RT 8.1
- Microsoft Windows Server 2012
- Microsoft Windows 8.1
- Microsoft Windows Server 2016
- Microsoft Windows Server 2008 R2
- Microsoft Windows 10
- Microsoft Windows 10 Servers
Classification
- Weakness
-
- CWE-404 Improper Resource Shutdown or Release
References
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2018-8410
patch, vendor-advisory
-
exploit-db.com
/exploits/45436/
exploit, third-party-advisory, vdb-entry
-
securitytracker.com
/id/1041635
vdb-entry, third-party-advisory
-
securityfocus.com
/bid/105256
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2018-8410
- NVD CVE-2018-8410
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.