CVE-2021-31955: Windows Kernel Information Disclosure Vulnerability
First published: Tue Jun 08 2021(Updated: )
Microsoft Windows Kernel contains an unspecified vulnerability that allows for information disclosure. Successful exploitation allows attackers to read the contents of kernel memory from a user-mode process.
Credit: secure@microsoft.com secure@microsoft.com secure@microsoft.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Microsoft Windows 10 | <10.0.17763.1999 | |
| Microsoft Windows 10 | <10.0.18363.1621 | |
| Microsoft Windows 10 | <10.0.19041.1052 | |
| Microsoft Windows 10 | <10.0.19042.1052 | |
| Microsoft Windows 10 | <10.0.19043.1052 | |
| Microsoft Windows Server 2004 | <10.0.19041.1052 | |
| Microsoft Windows Server 2019 | <10.0.17763.1999 | |
| Microsoft Windows Server 20H2 | <10.0.19042.1052 | |
| Windows 10 | =20h2 | |
| Windows 10 | =21h1 | |
| Windows 10 | =1809 | |
| Windows 10 | =1909 | |
| Windows 10 | =2004 | |
| Microsoft Windows Server 2016 | =20h2 | |
| Microsoft Windows Server 2016 | =2004 | |
| Microsoft Windows Server 2019 | ||
| Microsoft Windows Operating System |
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-2021-31955?
CVE-2021-31955 has a severity rating that indicates it can lead to information disclosure vulnerabilities in Microsoft Windows.
How do I fix CVE-2021-31955?
To fix CVE-2021-31955, ensure that you have the latest security updates installed for your affected version of Microsoft Windows.
Which versions of Windows are affected by CVE-2021-31955?
CVE-2021-31955 affects multiple versions of Microsoft Windows, including 10 (1809, 1909, 2004, 20H2, 21H1) and Windows Server (2016, 2019, 20H2).
What types of attacks can exploit CVE-2021-31955?
Exploitation of CVE-2021-31955 can allow attackers to read sensitive kernel memory from a user-mode process, posing a significant risk to system security.
Is there any known workaround for CVE-2021-31955?
Currently, there are no specific workarounds for CVE-2021-31955 other than applying the recommended patches from Microsoft.
- agent/first-publish-date
- agent/type
- agent/remedy
- agent/severity
- agent/title
- agent/description
- agent/weakness
- agent/event
- collector/mitre-cve
- source/MITRE
- agent/references
- agent/author
- agent/source
- agent/last-modified-date
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/nvd-cve
- collector/nvd-index
- agent/softwarecombine
- agent/tags
- exploited/true
- collector/cisa-known-exploited
- source/CISA
- vendor/microsoft
- canonical/microsoft windows 10
- canonical/microsoft windows server 2004
- canonical/microsoft windows server 2019
- canonical/microsoft windows server 20h2
- canonical/windows 10
- version/windows 10/20h2
- version/windows 10/21h1
- version/windows 10/1809
- version/windows 10/1909
- version/windows 10/2004
- canonical/microsoft windows server 2016
- version/microsoft windows server 2016/20h2
- version/microsoft windows server 2016/2004
- canonical/microsoft windows operating system