Local kernel-memory disclosure via improper object handling
Published May 21, 2020 · Updated Aug 19, 2026
Information disclosure in the Windows kernel allows local users to obtain memory information by running a crafted application. Microsoft identifies improper handling of in-memory objects as the fault but does not disclose the affected kernel routine, object type, or invalid operation. Successful exploitation requires an authenticated local session and exposes information useful for further compromise, without directly executing code or elevating rights.
Summary
What happened
Information disclosure in the Windows kernel allows local users to obtain memory information by running a crafted application. Microsoft identifies improper handling of in-memory objects as the fault but does not disclose the affected kernel routine, object type, or invalid operation. Successful exploitation requires an authenticated local session and exposes information useful for further compromise, without directly executing code or elevating rights.
The record
- CVE
- CVE-2020-1072
- Published
- May 21, 2020
- Updated
- Aug 19, 2026
- Vendor
- Microsoft
- Product
- Windows 10 Version 1507
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 21, 2020CVE publishedPublication date reported by the CVE source.
- Aug 19, 2026Record 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=10.0.10240.0 <publication
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
No sourced classifications are available.
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