YellowKey Bitlocker Bypass Vulnerability
github.comSeems like a backdoor.
What's the data in the FsTx folder? Is it just some magic data that Windows looks for?
Looks like it triggers a debug modus which in turn replay filesystem transactions from transaction logs?
Just a little help for the fellow TSA and FBI folks
Does anyone know if the fix was shipped already? If it not a backdoor, of course.
It does not matter. Who's gonna stop them adding a new backdoor in a later Windows Update(TM) ? T this point they are not to be trusted at all.
Microsoft doesn't need a back door, they can literally sign a new bootchain with the same certificate and install them on your computer.
This is a bug / vulnerability, not a back door.
"Who's going to stop <any OS or app> from inserting a backdoor at some random point in the future? They are not to be trusted at all."
How is this a backdoor if one of the steps is to reboot the system while holding down SHIFT? To boot in the first place, the drive needs to be unlocked.
The EFI partition is unencrypted.
“you don't even need to plug an external storage device, you can just pull out the disk, copy the files in the EFI partition, put it back and it will still work. That's how bad it is.”
If you have physical access to plug in a flash drive, why would you need the drive unlocked to reboot into the recovery environment? Just power it off and trigger the boot options
Most users have it unlocked by TPM only as that is the default Microsoft configuration - you then reboot into windows recovery, yes if windows recovery is disabled or if bitlocker requires a startup pin then this is mitigated.
"No, TPM+PIN does not help, the issue is still exploitable regardless, I asked myself this question, can it still work in a TPM+PIN environment ? Yes it does, I'm just not publishing the PoC, I think what's out there is already bad enough."
https://deadeclipse666.blogspot.com/2026/05/were-doing-silen...
Interesting. If TPM+PIN does not help, then what stands between Bitlocker and TPM unsealing the key?
Point taken, but I would call this an authentication bypass (i.e. you can become administrator without any credentials) instead of a BitLocker bypass. It looks like at most, having BitLocker turned on is a requirement to trigger the bug/backdoor.
In any case I'd be very curious to read a response to these findings from someone at Microsoft.
In addition to sibling comments, the author claims it also affects tpm+pin.