CVE-2018-0894 json
The Windows kernel in Microsoft Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1 and RT 8.1, Windows Server 2012 and R2, Wind…
published 2018-03-14 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-1685
- cvss
- 4.7
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.3%
- EPSS 2.3% chance of exploitation in 30 days, percentile 83%
- public exploits
- 1
- Exploit-DB
Summary
The Windows kernel in Microsoft Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1 and RT 8.1, Windows Server 2012 and R2, Windows 10 Gold, 1511, 1607, 1703, and 1709, Windows Server 2016 and Windows Server, version 1709 allows an information disclosure vulnerability due to the way memory addresses are handled, aka "Windows Kernel Information Disclosure Vulnerability". This CVE is unique from CVE-2018-0811, CVE-2018-0813, CVE-2018-0814, CVE-2018-0895, CVE-2018-0896, CVE-2018-0897, CVE-2018-0898, CVE-2018-0899, CVE-2018-0900, CVE-2018-0901 and CVE-2018-0926.
Patch / fix
Timeline
- Published
- First public exploit (EDB-44308)
Exploit prediction
2.34% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-44308 Microsoft Windows Kernel - 'NtQueryVirtualMemory(MemoryMappedFilenameInformation)' 64-bit Pool Memory Disclosure dos, 2018-03-20
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 4.7 | CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 1.9 | AV:L/AC:M/Au:N/C:P/I:N/A:N |
Affected products
- Microsoft Corporation Windows kernel
Classification
References
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2018-0894
patch, vendor-advisory
-
exploit-db.com
/exploits/44308/
exploit, third-party-advisory, vdb-entry
-
securitytracker.com
/id/1040517
vdb-entry, third-party-advisory
-
securityfocus.com
/bid/103231
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2018-0894
- NVD CVE-2018-0894
Fencer Vulns 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.