CVE-2018-0813
First published: Wed Mar 14 2018(Updated: )
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 objects are initialized in memory, aka "Windows Kernel Information Disclosure Vulnerability". This CVE is unique from CVE-2018-0811, CVE-2018-0814, CVE-2018-0894, CVE-2018-0895, CVE-2018-0896, CVE-2018-0897, CVE-2018-0898, CVE-2018-0899, CVE-2018-0900, and CVE-2018-0901 and CVE-2018-0926.
Credit: secure@microsoft.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Windows 10 | ||
| Windows 10 | =1511 | |
| Windows 10 | =1607 | |
| Windows 10 | =1703 | |
| Windows 10 | =1709 | |
| Microsoft Windows 7 | =sp1 | |
| Microsoft Windows | ||
| Microsoft Windows RT | ||
| Microsoft Windows Server | =1709 | |
| Microsoft Windows Server | =sp2 | |
| Microsoft Windows Server | =r2-sp1 | |
| Microsoft Windows Server | ||
| Microsoft Windows Server | =r2 | |
| Microsoft Windows Server 2016 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2018-0813?
CVE-2018-0813 has been categorized as a moderate severity information disclosure vulnerability.
How do I fix CVE-2018-0813?
To remediate CVE-2018-0813, users should apply the latest security updates provided by Microsoft for their respective operating systems.
Which systems are affected by CVE-2018-0813?
CVE-2018-0813 affects various versions of Microsoft Windows including Windows 7 SP1, Windows 10 (multiple builds), and multiple Windows Server editions.
What kind of information can be disclosed due to CVE-2018-0813?
CVE-2018-0813 can potentially lead to the exposure of sensitive information due to improper handling of objects in memory.
Is there a workaround for CVE-2018-0813 if I can't update immediately?
While the best solution is to apply the security updates, limiting user permissions and monitoring for unusual activities may serve as temporary mitigation.
- agent/type
- agent/severity
- agent/author
- agent/weakness
- agent/references
- agent/remedy
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/microsoft
- canonical/windows 10
- version/windows 10/1511
- version/windows 10/1607
- version/windows 10/1703
- version/windows 10/1709
- canonical/microsoft windows 7
- version/microsoft windows 7/sp1
- canonical/microsoft windows
- canonical/microsoft windows rt
- canonical/microsoft windows server
- version/microsoft windows server/1709
- version/microsoft windows server/sp2
- version/microsoft windows server/r2-sp1
- version/microsoft windows server/r2
- canonical/microsoft windows server 2016