Black Hat USA 2025 | BitUnlocker: Leveraging Windows Recovery to Extract BitLocker Secrets
Why It Matters
Because WinRE can now be weaponized to bypass BitLocker, organizations risk data breaches even when disks are encrypted, compelling immediate remediation and revisiting of physical‑security controls.
Key Takeaways
- •WinRE can be manipulated to bypass BitLocker encryption
- •Vulnerability allows loading arbitrary WIM image via SDI offset
- •Modified recovery XML enables execution of signed tools for data extraction
- •Researchers disclosed fixes and recommended hardening recovery environment
- •Physical attackers can now retrieve secrets without BitLocker key
Summary
At Black Hat USA 2025, Microsoft’s Storm team unveiled “Bit Unlocker,” a proof‑of‑concept that abuses the Windows Recovery Environment (WinRE) to extract BitLocker keys and decrypt protected volumes.
The researchers explained that WinRE runs from a separate recovery partition and loads a trusted WIM image (winre.wim) into RAM. Design changes—moving winre.wim to an unencrypted volume, introducing a hash‑based “trusted‑wim” check, and auto‑unlocking the OS volume unless a risky tool is invoked—create a narrow but powerful attack surface. By manipulating the SDI boot file’s offset, an attacker can append an untrusted WIM that passes the hash check yet executes arbitrary code while the OS volume remains unlocked.
A live demo showed a locked machine being rebooted into WinRE, the exploit loading a malicious WIM, and the OS volume instantly reporting “unlocked” while BitLocker protection stayed enabled, exposing all files. The team also identified a second vector in the recovery‑agent XML, where scheduled offline‑scan operations can be redirected to signed utilities such as TTTracer, which can then trace and launch cmd.exe to harvest secrets.
These findings demonstrate that pre‑OS components can defeat full‑disk encryption, forcing enterprises to patch WinRE, enforce stricter signing policies, and consider additional hardware‑based protections. Microsoft has already issued mitigations, but the research underscores the need for continuous hardening of boot‑time environments.
Comments
Want to join the conversation?
Loading comments...