Protected-memory disclosure via speculative CPU access
Published Apr 15, 2020 · Updated Aug 4, 2024
Information disclosure in the Windows kernel on affected Windows releases allows local users to read protected memory through speculative CPU access. Microsoft has not disclosed the exact kernel locus or operation beyond certain CPUs speculatively accessing memory. Low-privilege local code execution is required; the published assessment reports no integrity or availability impact.
Summary
What happened
Information disclosure in the Windows kernel on affected Windows releases allows local users to read protected memory through speculative CPU access. Microsoft has not disclosed the exact kernel locus or operation beyond certain CPUs speculatively accessing memory. Low-privilege local code execution is required; the published assessment reports no integrity or availability impact.
The record
- CVE
- CVE-2020-0955
- Published
- Apr 15, 2020
- Updated
- Aug 4, 2024
- Vendor
- Microsoft
- Product
- Windows 10 Version 1909
- Classifications
- T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 15, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo