As reported by The Hacker News, researchers at Technische Universität Berlin have disclosed a hardware-based attack that effectively neutralizes the TPM lockout mechanism protecting Windows Hello and BitLocker PINs on systems using firmware TPMs (fTPM). The implications are significant: attack timelines collapse from years to hours, and the root cause is architectural rather than a simple software bug.

Security Impact: As reported by The Hacker News, researchers at Technische Universität Berlin have disclosed a hardware-based attack that effectively neutralizes the TPM lockout mechanism protecting Windows Hello and BitLocker PINs on systems using firmware TPMs (fTPM).

Why This Matters

The fundamental issue is that fTPM implementations on AMD and some Intel processors lack dedicated secure storage. Instead, they persist encrypted state — including the wrong-guess counter — on the mainboard's SPI flash chip. This design decision creates a rollback window: an attacker with physical access can snapshot the flash, restore it after failed attempts, and reset the counter indefinitely.

The researchers identified two distinct attack paths against the RPMC (Replay Protected Memory Counters) mechanism designed to prevent exactly this:

  • AMD firmware gap: On AMD systems using RPMC-equipped flash chips, the processor firmware never verifies that the counter actually increased. A simple interposer board between the CPU and flash can block the counter update while reporting success.
  • Winbond voltage glitch: On systems using Winbond RPMC flash, a brief voltage glitch extracts the signing key in approximately one second. On the Intel laptop tested, the firmware fed the chip the same value at every boot, meaning the leaked key persisted across restarts.

Vulnerability Details

FieldDetail
Affected VendorAMD (confirmed), Intel (partial)
Affected ComponentFirmware TPM (fTPM), RPMC flash counters
Confirmed Test SystemsHP OmniBook 3 (AMD Ryzen AI 5 330), Intel-based laptop (model not disclosed)
Attack TypePhysical access, hardware interposer, voltage glitching
Patch StatusAMD: fixes planned November 2026 – February 2027. Intel: status not confirmed.
Active ExploitationNone reported; proof-of-concept demonstrated in lab
Worst-Case Impact4-digit Hello PIN: ~40 hours (vs. 69 days). 6-digit BitLocker PIN: ~20 days (vs. 19 years).

Who Is at Risk

This attack requires physical access — opening the PC case and attaching hardware. That narrows the threat model considerably but does not eliminate it. The most exposed environments include:

Vulnerability Details
Stolen or lost laptops: Devices with full-disk encryption are assumed to resist offline attacks. This research shows that assumption breaks for fTPM-protected systems with short PINs.
High-value targets: Executives, government employees, and researchers whose devices may be specifically targeted. A 20-day window to crack a 6-digit BitLocker PIN is well within an adversary's operational patience.
Shared or accessible workspaces: Any environment where an attacker can briefly access unattended hardware.
The default assumption that TPM lockout makes short PINs safe is now demonstrably false for a large class of consumer and enterprise hardware.

Shield53 Recommendations

Immediate Actions

  • Increase PIN length now. The researchers recommend adding at least two digits. For BitLocker, move to 8+ digits. For Windows Hello, use 8+ digits or switch to a passphrase. Every additional digit multiplies brute-force time by roughly 10x.
  • Prefer dTPM where available. Discrete TPM 2.0 chips have their own secure storage and are not vulnerable to this specific flash-rollback attack. Where hardware supports it, configure the system to use the discrete TPM rather than the firmware TPM.
  • Enable additional authentication factors. For Windows Hello, combine PIN with biometric or hardware key requirements. For BitLocker, consider multi-factor authentication using a smart card or FIDO2 token where the deployment supports it.
  • Monitor for firmware updates. AMD has committed to fixes between November 2026 and February 2027. Track your vendor's advisory pages and apply fTPM firmware updates as soon as they are released. Intel's response status remains unclear — press your vendor for clarity.
  • Reassess physical security posture. For high-value assets, treat physical access as equivalent to compromise. Use cable locks, secure storage when unattended, and consider tamper-evident seals for sensitive workstations.
  • Review BitLocker recovery policies. Ensure recovery keys are escrowed properly and that recovery mechanisms themselves do not become the weaker link.

Broader Implications

This research highlights a recurring pattern in hardware security: mechanisms that are theoretically sound fail because implementations cut corners. The AMD firmware not verifying RPMC counter increments is not an exotic flaw — it is a missing validation step. The Winbond voltage glitch vulnerability underscores that even hardened counter chips can leak their secrets under fault injection. Defenders should assume that any security boundary dependent on a single hardware component's integrity is fragile, and design depth accordingly. For now, lengthening PINs is the fastest, cheapest, and most effective mitigation available.