UEFI code execution via trusted vulnerable boot manager
Published May 9, 2023 · Updated Jul 10, 2025
Secure Boot bypass in Microsoft Windows allows attackers with local administrative or physical access to execute self-signed UEFI code. The Windows Boot Manager continues to trust vulnerable boot managers signed by the Windows Production PCA 2011 certificate, allowing a crafted loader to start despite Secure Boot. Secure Boot must be enabled, and exploitation grants pre-OS persistence and defense evasion to an attacker who already has administrative or physical access.
Summary
What happened
Secure Boot bypass in Microsoft Windows allows attackers with local administrative or physical access to execute self-signed UEFI code. The Windows Boot Manager continues to trust vulnerable boot managers signed by the Windows Production PCA 2011 certificate, allowing a crafted loader to start despite Secure Boot. Secure Boot must be enabled, and exploitation grants pre-OS persistence and defense evasion to an attacker who already has administrative or physical access.
The record
- CVE
- CVE-2023-24932
- Published
- May 9, 2023
- Updated
- Jul 10, 2025
- Vendor
- Microsoft
- Product
- Windows 10 Version 1507
- Classifications
- CWE-863, T1547
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- May 9, 2023CVE publishedPublication date reported by the CVE source.
- Jul 10, 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.21073
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.
Reported exploitation
- BlackLotus UEFI bootkit exploitationreported exploitation
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