Local privilege escalation via improperly locked memory
Published Jun 13, 2023 · Updated Jan 1, 2025
Improperly locked memory in the Windows Bus Filter Driver in Windows 11 version 22H2 allows local users to elevate privileges. Microsoft identifies sensitive data storage in improperly locked memory but has not published the affected routine, stored data, or exploitation sequence. Exploitation requires existing low-privileged local access and high-complexity conditions; successful attacks can compromise confidentiality, integrity, and availability.
Summary
What happened
Improperly locked memory in the Windows Bus Filter Driver in Windows 11 version 22H2 allows local users to elevate privileges. Microsoft identifies sensitive data storage in improperly locked memory but has not published the affected routine, stored data, or exploitation sequence. Exploitation requires existing low-privileged local access and high-complexity conditions; successful attacks can compromise confidentiality, integrity, and availability.
The record
- CVE
- CVE-2023-32010
- Published
- Jun 13, 2023
- Updated
- Jan 1, 2025
- Vendor
- Microsoft
- Product
- Windows 11, version 22H2
- Classifications
- CWE-591, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 13, 2023CVE publishedPublication date reported by the CVE source.
- Jan 1, 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.22621.0 <10.0.22621.1848
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
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