Physical security bypass via heap buffer overflow
Published Jan 10, 2023 · Updated Jan 1, 2025
A heap-based buffer overflow in Microsoft Windows Boot Manager allows physically proximate attackers with low privileges to bypass boot security. Microsoft identifies the component and weakness class but has not published the input, parsing operation, or overwritten heap object. Exploitation requires physical access and low privileges; success compromises confidentiality, integrity, and availability within the existing security scope.
Summary
What happened
A heap-based buffer overflow in Microsoft Windows Boot Manager allows physically proximate attackers with low privileges to bypass boot security. Microsoft identifies the component and weakness class but has not published the input, parsing operation, or overwritten heap object. Exploitation requires physical access and low privileges; success compromises confidentiality, integrity, and availability within the existing security scope.
The record
- CVE
- CVE-2023-21560
- Published
- Jan 10, 2023
- Updated
- Jan 1, 2025
- Vendor
- Microsoft
- Product
- Windows 10 Version 1507
- Classifications
- CWE-122
- Attack vector
- physical
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 10, 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.10240.0 <10.0.10240.19685
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
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