FastUnlock: how to protect a PC with BitLocker against the Windows flaw

FastUnlock: how to protect a PC with BitLocker against the Windows flaw

FastUnlock allows someone with physical access to a locked PC to run programs without signing in, according to tests by ThreatLocker. The technique uses Narrator and the Microsoft account recovery flow; the company gained access to WSIAccount, a non-administrator account. No official list of affected versions has been published, and Microsoft has not yet released a patch.

The vulnerability does not decrypt BitLocker or recover its key: it acts when the computer has already started Windows and the drive is unlocked. The Hacker News notes that there is no evidence of use in real-world attacks; ThreatLocker describes a proof of concept that required an external drive to introduce code, though it says there are other ways to get it onto the computer.

Check whether your computer meets the conditions

Consider the computer potentially exposed if someone could physically tamper with it and the lock screen allows access to Microsoft account recovery options. The technique uses Narrator, Windows’ built-in screen reader, to navigate the lock screen and access settings.

There is no official list of vulnerable versions. Although the issue has been described as a Windows 11 flaw, The Hacker News does not provide a list of versions and recommends treating computers that meet the conditions above as potentially affected. Tom’s Hardware mentions Windows 11 and possibly Windows 10, but does not confirm the definitive scope.

ThreatLocker says its test reached WSIAccount, without administrator privileges. This limits the type of access observed: it is not equivalent to taking administrative control of the PC. Even so, the ability to run programs from the device warrants protecting it from anyone who might get their hands on it.

Steps to reduce the risk

  1. Control who can physically access the computer. Lock away laptops that could be lost, and monitor computers in shared workspaces or visitor-accessible reception areas. FastUnlock’s central requirement is physical access: reducing that exposure removes the necessary condition for attempting it.

  2. Set a BitLocker startup PIN on sensitive computers. ThreatLocker says a pre-boot PIN helps mitigate the technique if the device has just been turned on. The Hacker News explains that, with a common configuration, the TPM automatically unlocks the drive; the PIN requires a code to be entered before Windows starts and accesses the drive.

  3. Shut down or hibernate the computer when it will be out of your control. The startup PIN protects a device that has not yet started Windows, not one that is already at the lock screen with the drive unlocked. The Hacker News includes this recommendation alongside using a PIN against attackers with physical access.

  4. Review how the Microsoft account can be recovered from the lock screen. The described technique depends on an account being available through that flow. Do not assume that the lock screen alone prevents someone from exploring options accessible through Narrator.

  5. Apply an official patch when one becomes available. The Hacker News reports that Microsoft had not yet released a fix. Watch for updates and apply the correction when Microsoft distributes it; until then, prioritize physical access controls and startup protection.

Mistakes to avoid

Do not confuse encryption with protection after startup. BitLocker protects the data on the drive, but in the automatic configuration described, the TPM unlocks it when Windows starts. FastUnlock does not break the encryption: the technique runs after that unlock, so having BitLocker enabled is not enough to rule out the risk.

Do not rely on the lock screen alone. FastUnlock specifically relies on features available from it. If the computer is on and someone can access it physically, the sign-in screen is no substitute for a pre-boot PIN or keeping the device under control.

Do not overstate the access demonstrated. ThreatLocker tested access to WSIAccount, which is not an administrator account. Tom’s Hardware suggests broader consequences, but the tests described by ThreatLocker do not establish that an attacker automatically obtains an administrator account or can read all files.

Do not treat a claim as an official list. There is no confirmed inventory of affected versions. If your computer meets the physical access and account recovery conditions, take preventive measures without assuming that a particular edition is exempt.

ThreatLocker also observed that it could not type using the physical keyboard while navigating Narrator, although it was able to open the on-screen keyboard when it needed to enter text. That limitation does not eliminate the problem: in its test, the company managed to run code from the computer.

Sources: ThreatLocker, The Hacker News, Tom's Hardware