Local code execution via undisclosed use-after-free
Published Jun 13, 2023 · Updated Jan 1, 2025
Use-after-free in Windows Hello in Microsoft Windows 11 version 22H2 allows local users to execute code after user interaction. Microsoft identifies the weakness but has not disclosed the affected routine, object-lifetime error, or attacker-controlled input. Exploitation requires an action on the local system and executes the attacker's code in the affected user's security context.
Summary
What happened
Use-after-free in Windows Hello in Microsoft Windows 11 version 22H2 allows local users to execute code after user interaction. Microsoft identifies the weakness but has not disclosed the affected routine, object-lifetime error, or attacker-controlled input. Exploitation requires an action on the local system and executes the attacker's code in the affected user's security context.
The record
- CVE
- CVE-2023-32018
- Published
- Jun 13, 2023
- Updated
- Jan 1, 2025
- Vendor
- Microsoft
- Product
- Windows 11, version 22H2
- Classifications
- CWE-416, T1203
- Attack vector
- local
- Privileges
- unauthenticated
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?
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.
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