Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
BitUnlocker — Downgrade attack for CVE-2025-48804 | Kitploit
Tools/GitHubGitHub/garatc/bitunlocker
Vulnerability AnalysisExploitationPost-ExploitationPenetration TestingHardware SecurityRed Teaming
GitHubgaratc/bitunlocker

BitUnlocker

Downgrade attack for CVE-2025-48804

View Repository
223443820 days agoReviewed by Kitploit
Share

BitUnlocker Downgrade Attack

License: MIT

A proof of concept for accessing BitLocker-encrypted disks in under 5 minutes on fully patched Windows 11 machines through a boot manager downgrade attack, leveraging the SDI vulnerability originally documented as CVE-2025-48804. The July 2025 patch fixes this in bootmgfw.efi, so any pre-patch bootmgfw.efi can be used for a downgrade attack, provided the target does not enforce a boot-manager version (SVN) (which comes with KB5025885).

This PoC provides two delivery methods: USB boot (simpler and recommended) and PXE boot and hints at a riskier method you could use when neither PXE nor USB is allowed.

This work builds entirely on the research by Microsoft STORM (Netanel Ben Simon and Alon Leviev):

BitUnlocker: Leveraging Windows Recovery to Extract BitLocker Secrets


Prerequisites

  • Physical access to a BitLocker-encrypted device (TPM-only - or TPM+PIN with a PIN you know, PCR 7 + 11)
  • The device does not enforce SVN

Step-by-step

1. Download boot_patched.sdi from Releases (or build your own SDI file, see below)

Put it in USB/sdi/ (for USB method) or TFTP-root/sdi/ (for PXE method).

2. Prepare the modified BCD (skip if neither USB nor PXE is available on your target)

On the target device, open a WinRE command prompt (hold Shift while clicking Restart, then Troubleshoot > Command Prompt — click "Ignore this disk" when prompted for a BitLocker recovery key and click "relaunch" if you're also told that the cmd prompt cannot run on a locked device — and if the cmd prompt just won't open, use your own WinPE if you can). Plug in a USB stick and run:

E: (or wherever your USB is)
bcdedit /export BCD_modded
bcdedit /store BCD_modded /set {default} path \WINDOWS\system32\winload_DOESNOTEXIST.efi
bcdedit /store BCD_modded /enum all

In the output, find the device options entry whose description is "Windows Recovery" and which contains ramdisksdidevice / ramdisksdipath entries. Note its GUID, then:

bcdedit /store BCD_modded /set {GUID} ramdisksdidevice boot
bcdedit /store BCD_modded /set {GUID} ramdisksdipath \sdi\boot_patched.sdi
move BCD_modded BCD

Place the resulting BCD file in the appropriate location depending on your method:

  • USB: USB/EFI/Microsoft/Boot/BCD
  • PXE: TFTP-root/Boot/BCD

3. Check target boot manager signature

This will be important for the next steps, so take note whether it is signed by PCA 2011 or CA 2023: we want to use a downgrade boot manager that is signed by the same CA as the target's boot manager to avoid PCR 7 mismatch and actually unlock the BitLocker-encrypted drive.

Machines freshly installed since early 2026 likely ship with a CA 2023-signed bootmgfw.efi by default. To check which CA is used, mount the EFI partition and inspect the active binary: mountvol S: /s then sigcheck -i S:\EFI\Microsoft\Boot\bootmgfw.efi (sigcheck is a free Sysinternals tool). Note that C:\Windows\Boot\EFI\bootmgfw.efi may differ from the file actually used at boot - always check the EFI partition copy. If you see "Windows UEFI CA 2023", then the boot manager is signed by CA 2023. If you see "Microsoft Windows Production PCA 2011", the boot manager is signed by PCA 2011.

4. Boot the target

Option A: USB boot (recommended)

Format a USB stick as FAT32 and copy the contents of the USB/ directory to its root (only its content, there should not be a "USB" folder). The USB stick should look like this:

USB stick root/
├── EFI/
│   ├── Boot/
│   │   └── bootx64.efi        # Pre-patch boot manager (PCA 2011)
│   │   └── bootx64_CA2023.efi # Pre-patch boot manager (CA 2023)
│   └── Microsoft/
│       └── Boot/
│           └── BCD             # Your modified BCD
└── sdi/
    └── boot_patched.sdi        # Patched SDI with custom WinRE

Plug the USB stick into the target and trigger a UEFI USB boot — either from WinRE (Use a device) or by pressing the manufacturer's boot menu key at power-on (F12, F9, etc.). If the USB stick doesn't appear in the list of boot options, look for a "Boot from file" option in the UEFI boot menu, then navigate to EFI/Boot/bootx64.efi on the USB stick if your target has a 2011-signed boot manager, otherwise use EFI/Boot/bootx64_CA2023.efi. If you chose to boot automatically (so, not through the "Boot from file" option) and the boot manager is signed by CA2023, make sure you rename bootx64_CA2023.efi to bootx64.efi.

Option B: PXE boot

The TFTP-root/ directory is structured as follows:

TFTP-root/
├── bootmgfw.efi                # Pre-patch boot manager (PCA 2011)
├── bootmgfw_CA2023.efi         # Pre-patch boot manager (CA 2023)
├── Boot/
│   └── BCD                     # Your modified BCD
├── EFI/
│   └── Microsoft/
│       └── Boot/
│           └── bootmgfw.efi           # Same pre-patch boot manager (PCA 2011)
│           └── bootmgfw_CA2023.efi    # Same pre-patch boot manager (CA 2023)
└── sdi/
    └── boot_patched.sdi        # Patched SDI with custom WinRE

If your target's boot manager is signed by CA 2023, you want to rename TFTP-root/bootmgfw_CA2023.efi and TFTP-root/EFI/Microsoft/Boot/bootmgfw_CA2023.efi to TFTP-root/bootmgfw.efi and TFTP-root/EFI/Microsoft/Boot/bootmgfw.efi respectively.

Then, connect the target to your Linux machine via Ethernet and start the PXE server:

cd BitUnlocker
export INTERFACE=<your-interface>
export ABS_TFTP_ROOT=$(pwd)/TFTP-root

sudo ifconfig $INTERFACE 10.13.37.1
sudo dnsmasq --no-daemon \
  --interface="$INTERFACE" \
  --dhcp-range=10.13.37.100,10.13.37.101,255.255.255.0,1h \
  --dhcp-boot=bootmgfw.efi \
  --enable-tftp \
  --tftp-root="$ABS_TFTP_ROOT" \
  --log-dhcp \
  --tftp-max=65464 \
  --port=0

Trigger PXE boot on the target — from WinRE select Use a device > IPv4 Network, or press the manufacturer's PXE boot key.

Option C: no USB or PXE boot allowed

Another option is to just stage the SDI file inside the ESP or Recovery partition, since write access is provided to those from WinRE. The only limiting factor is free space, as those partitions are generally quite tight. But with the SDI file being smaller in the recent Release (~115Mb), it will likely fit. Note that you will directly be modifying the boot manager as well as the BCD of your target, so it is a bit more involved. Replacing the boot manager with a version that's not signed by the same PCA will cause PCR mismatch and therefore a BitLocker blue screen, and you will also tamper with WinRE itself, making it unable to load (and help you debug) if you mess up.

I will not give any more details, do it only if PXE and USB aren't available and if you know what you are doing. Do it at your own risk, I will not be responsible if you can't boot your PC anymore.

5. Wait for the SDI transfer

The boot manager will load the BCD, then start downloading boot_patched.sdi. The SDI file is large (~300 MB) so this takes a moment from USB, or several minutes over TFTP. A recovery-related message with the SDI path should appear on the target screen while it loads.

6. Profit

Once the transfer completes, a command prompt should appear with the OS volume decrypted and mounted (typically C: or E:). If it wasn't mounted automatically or you don't want to guess the letter, just run diskpart -> sel vol X (the one that looks like your encrypted drive) -> assign letter=C (or something else) -> (wait for a bit) -> exit -> profit

Edge cases

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    867
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    544
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    385
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    360
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    302
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    279

Explore all tools

Browse our collection of tools

View all tools →