Local kernel-memory disclosure via undisclosed mechanism
Published Oct 11, 2022 · Updated Jan 2, 2025
Information disclosure in the Microsoft Windows kernel allows local users to read kernel memory through an undisclosed local vector. Microsoft's public record identifies the kernel as the affected component but does not identify the routine, data structure, or incorrect operation that exposes memory. Successful access requires low local privileges and no user interaction; the documented consequence is limited to confidentiality loss.
Summary
What happened
Information disclosure in the Microsoft Windows kernel allows local users to read kernel memory through an undisclosed local vector. Microsoft's public record identifies the kernel as the affected component but does not identify the routine, data structure, or incorrect operation that exposes memory. Successful access requires low local privileges and no user interaction; the documented consequence is limited to confidentiality loss.
The record
- CVE
- CVE-2022-37996
- Published
- Oct 11, 2022
- Updated
- Jan 2, 2025
- Vendor
- Microsoft
- Product
- Windows 10 Version 1507
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 11, 2022CVE publishedPublication date reported by the CVE source.
- Jan 2, 2025Record 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 <10.0.10240.19507
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