· via Hacker News – Front Page (native)
Researchers exploit TPM flash counter flaws to brute-force Windows Hello PINs
An arXiv paper shows how flaws in Winbond flash chips and AMD's TPM firmware let attackers roll back lockout counters, cracking a 4-digit Windows Hello PIN in 40 hours instead of 69 days.

What happened
Security researchers have published what they describe as the first practical analysis of Replay Protected Monotonic Counters (RPMC) — the flash-chip mechanism modern x86 platforms use to detect tampering with TPM state. The paper, which appeared on arXiv on 13 November and reached the Hacker News front page on 17 November, identifies implementation flaws that let an attacker with physical access reset a TPM's anti-hammering lockouts and brute-force Windows Hello PINs in hours rather than weeks.
Why four-digit PINs exist at all
According to the paper, Windows Hello is the primary authentication mechanism on more than one billion Windows 11 devices, and it accepts PINs as short as four digits. Low-entropy secrets like these are viable only because the Trusted Platform Module throttles repeated wrong guesses and eventually locks an attacker out entirely.
Most modern x86 machines implement the TPM in firmware. An fTPM stores its non-volatile state — including the lockout counters — in SPI flash. On newer platforms, preventing an attacker from writing back an older flash image, and with it an older unlocked state, is delegated to the flash chip itself through RPMC, a JEDEC-standard counter mechanism that operates over the SPI bus. That bus, the researchers note, is physically accessible to anyone who can open the machine.
Two flaws that defeat the counter
Using inexpensive interposer hardware placed between the platform and the flash chip, the researchers identified several implementation flaws, two of which they say gut RPMC's security model.
The first lives in Winbond SPI flash. Winbond is the leading NOR flash vendor with over 25 percent market share, according to the paper, and its chips can be coaxed into revealing the HMAC key that protects the counter through voltage glitching. With that key in hand, arbitrary counter values can be forged.
The second lives in AMD's firmware: the NV controller never verifies that a counter increment actually occurred, so hardware sitting on the bus can silently drop those commands without the fTPM noticing.
The researchers add a third finding for AMD boards that ship without RPMC-capable flash: these appear to have no NV rollback protection at all. On two AMD desktops, simply reflashing an older image was enough to reset the fTPM's lockout counters.
From 69 days to 40 hours
Either flaw is sufficient to roll back an fTPM's non-volatile state — on AMD, Intel, or Pluton platforms — including its lockout counters. The researchers demonstrated the attack end to end on locked, encrypted hardware: their setup found a four-digit Windows Hello PIN in 40 hours, a search the TPM's throttling would otherwise stretch to 69 days.
The damage extends past the login screen. Per the paper, a compromised PIN also grants access to device-bound keys and Hello-based enterprise single sign-on. The same rollback primitive defeats BitLocker's TPM+PIN pre-boot protector, cutting the worst-case time for a default six-digit PIN from 19 years to 20 days.
Why it matters
The attack requires physical access and low-cost hardware, so it is not a remote threat. But it collapses the time budget for targeted attacks on stolen or seized laptops from weeks or years down to days, and BitLocker's TPM+PIN protector is commonly recommended for machines that face exactly this kind of risk.
The research also shows how thin the hardware guarantee behind short PINs really is. Anti-hammering is the sole reason four-digit PINs are considered acceptable, and this paper demonstrates that on shipping systems that protection ultimately rests on a commodity flash chip and vendor firmware that, in the authors' accounting, had never been practically audited in this way. Because Winbond holds more than a quarter of the NOR flash market, a single vendor's silicon decision affects a large share of machines in the field.
Remediation will not be quick. The Winbond flaw sits in the chip itself, and AMD's fix requires firmware changes across affected platforms; the abstract says nothing about disclosure timelines, patches, or affected product lists. In the meantime, the researchers' own numbers argue for longer PINs and passwords: six digits buys 20 days of resistance rather than 40 hours.
- #security
- #windows-hello
- #tpm
- #hardware
- #bitlocker