跳到正文
研踪PaperTrail
← 研踪 PaperTrail

arXiv:2611.18126 · v1

Hello Again: Exploiting Replay Protected Monotonic Counters to Brute-Force Windows Hello PINs

首次提交 2026-11-13 20:53
版本更新 2026-11-13 20:53
雷达观测 2026-11-16 11:41
arXiv ↗PDF ↗

摘要

Windows Hello is the primary authentication mechanism on over one billion Windows 11 devices, supporting PINs as short as four digits. Such low-entropy PINs are viable only because the TPM's anti-hammering protection mitigates brute-force attacks. Most modern x86 platforms rely on firmware TPMs (fTPMs) that persist their non-volatile (NV) state, including the lockout state, to SPI flash. On newer platforms, rollback prevention of this state is delegated to the flash chip via Replay Protected Monotonic Counters (RPMCs), a JEDEC-standardized mechanism operating over a physically accessible bus. We present the first practical security analysis of RPMC in shipping x86 systems. Using low-cost interposer hardware, we identify multiple implementation flaws, two of which fundamentally undermine RPMC's security model: First, Winbond SPI flash - the leading NOR flash vendor with over 25% market share - leaks its HMAC key under voltage glitching, enabling arbitrary counter forgery. Second, AMD's NV controller does not verify RPMC increments, so an interposer can suppress them unnoticed. Moreover, AMD platforms without RPMC flash appear to lack NV rollback protection altogether: on two AMD desktops, reflashing an old image resets the fTPM's lockout counters. Both flaws enable rollbacks of the fTPM's NV state (AMD, Intel, or Pluton), including its lockout counters. We demonstrate this end-to-end on locked, encrypted hardware: our setup finds a 4-digit Windows Hello PIN in 40 hours instead of 69 days. A compromised PIN also grants access to device-bound keys and Hello-based enterprise SSO. The same primitive defeats BitLocker's TPM+PIN pre-boot protector, reducing the worst-case time for a default-length 6-digit PIN from 19 years to 20 days.

作者备注:This is a slightly updated version of the paper published at ACM CCS '26 (https://doi.org/10.1145/3830454.3846631). The section Changes from the CCS '26 Version lists all changes

AI 论文解读

基于摘要 · 非全文审阅

此版本尚未生成 AI 解读。解读由后台任务生成并按论文版本保存,登录后共享已有结果。

版本差异

目前只收录了一个版本。收录下一版后,可以对照标题、作者、分类和摘要。

观测到的版本

相邻记录可能跳过中间版本;首次发现 v2 及以上也会标为版本更新。

v1 · 2026-11-13 20:53 · 最新观测版本

Hello Again: Exploiting Replay Protected Monotonic Counters to Brute-Force Windows Hello PINs

Windows Hello is the primary authentication mechanism on over one billion Windows 11 devices, supporting PINs as short as four digits. Such low-entropy PINs are viable only because the TPM's anti-hammering protection mitigates brute-force attacks. Most modern x86 platforms rely on firmware TPMs (fTPMs) that persist their non-volatile (NV) state, including the lockout state, to SPI flash. On newer platforms, rollback prevention of this state is delegated to the flash chip via Replay Protected Monotonic Counters (RPMCs), a JEDEC-standardized mechanism operating over a physically accessible bus. We present the first practical security analysis of RPMC in shipping x86 systems. Using low-cost interposer hardware, we identify multiple implementation flaws, two of which fundamentally undermine RPMC's security model: First, Winbond SPI flash - the leading NOR flash vendor with over 25% market share - leaks its HMAC key under voltage glitching, enabling arbitrary counter forgery. Second, AMD's NV controller does not verify RPMC increments, so an interposer can suppress them unnoticed. Moreover, AMD platforms without RPMC flash appear to lack NV rollback protection altogether: on two AMD desktops, reflashing an old image resets the fTPM's lockout counters. Both flaws enable rollbacks of the fTPM's NV state (AMD, Intel, or Pluton), including its lockout counters. We demonstrate this end-to-end on locked, encrypted hardware: our setup finds a 4-digit Windows Hello PIN in 40 hours instead of 69 days. A compromised PIN also grants access to device-bound keys and Hello-based enterprise SSO. The same primitive defeats BitLocker's TPM+PIN pre-boot protector, reducing the worst-case time for a default-length 6-digit PIN from 19 years to 20 days.

查看此版本解读 →查看此版本原文 ↗