Encrypted-data access via attacker-supplied SYSTEM hive
Published Jan 9, 2024 · Updated May 3, 2025
BitLocker bypass in Windows Recovery Environment allows physically proximate attackers to access encrypted data on affected Windows systems. Winload honors an attacker-controlled systemdatadevice entry and loads an external SYSTEM hive whose Setup!CmdLine launches a SYSTEM shell in WinRE. Physical access and low privileges are required; the shell exposes BitLocker keys already present in memory and grants access to protected volumes.
Summary
What happened
BitLocker bypass in Windows Recovery Environment allows physically proximate attackers to access encrypted data on affected Windows systems. Winload honors an attacker-controlled systemdatadevice entry and loads an external SYSTEM hive whose Setup!CmdLine launches a SYSTEM shell in WinRE. Physical access and low privileges are required; the shell exposes BitLocker keys already present in memory and grants access to protected volumes.
The record
- CVE
- CVE-2024-20666
- Published
- Jan 9, 2024
- Updated
- May 3, 2025
- Vendor
- Microsoft
- Product
- Windows 10 Version 1507
- Classifications
- CWE-693, T1005
- Attack vector
- physical
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 9, 2024CVE publishedPublication date reported by the CVE source.
- May 3, 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.20402
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.
Public exploit references
- break out in hivesfunctional · demonstrated
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