Kernel-memory disclosure via mishandled CLFS objects
Published Feb 11, 2020 · Updated Aug 4, 2024
Information disclosure in the Microsoft Windows CLFS driver allows local users to read kernel memory through crafted CLFS activity. The driver improperly handles in-memory objects during CLFS processing, but Microsoft has not disclosed the specific object-lifecycle or bounds error. Low-privilege local access is required, and exploitation exposes kernel-memory contents without altering data or interrupting service.
Summary
What happened
Information disclosure in the Microsoft Windows CLFS driver allows local users to read kernel memory through crafted CLFS activity. The driver improperly handles in-memory objects during CLFS processing, but Microsoft has not disclosed the specific object-lifecycle or bounds error. Low-privilege local access is required, and exploitation exposes kernel-memory contents without altering data or interrupting service.
The record
- CVE
- CVE-2020-0658
- Published
- Feb 11, 2020
- Updated
- Aug 4, 2024
- Vendor
- Microsoft
- Product
- Windows 10 Version 1909
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 11, 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
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