HP ThinPro TPM Flaw Allows Physical Extraction of LUKS Encryption Keys
A boot-chain vulnerability in HP ThinPro 8 and 9 enables attackers with physical access to extract LUKS disk-encryption keys by manipulating the initramfs.
A critical security flaw has been identified in HP's ThinPro 8 and 9 operating systems, allowing attackers with physical access to a thin client to extract the LUKS disk-encryption key. This vulnerability affects HP thin clients that utilize LUKS2 for protecting the operating system's encrypted root partition, with the decryption key typically sealed within the device's Trusted Platform Module (TPM).
The intended security mechanism relies on the TPM to prevent data theft from removed storage drives. However, a security researcher discovered that the TPM policy does not sufficiently validate the software loaded during the boot process. HP ThinPro employs a utility called hptc-tpm-tool to retrieve the LUKS key from the TPM during startup. An initramfs script, unseal_key, requests this key and passes it to cryptsetup to unlock the encrypted root partition.
The core of the vulnerability lies in the TPM key sealing process. The key is reportedly sealed only to specific Platform Configuration Registers (PCRs) – PCR 0, PCR 2, and PCR 4. These registers measure critical boot components like the BIOS firmware, option ROMs or UEFI drivers, and the GRUB bootloader binary. Crucially, they do not measure GRUB configuration commands, the Linux kernel, or the initramfs loaded by GRUB.
This oversight creates a significant attack vector. While an attacker cannot easily replace the GRUB binary without altering PCR 4 and preventing key release, they can modify the unencrypted initramfs. This includes altering the unseal_key script itself, without triggering any TPM integrity checks because the measured PCR values remain unchanged. The researcher confirmed this on HP t530 and t540 models running ThinPro 8.1.0 and 9.0.0 respectively.
Once the initramfs is compromised, a modified script can copy the recovered LUKS key to the unencrypted BOOT partition before the system fully boots. The TPM, unaware of the initramfs modification, proceeds with the boot process, treating the system as trusted because the firmware and GRUB measurements are intact. The attacker can then retrieve the exposed LUKS key from the drive at a later time.
This attack requires direct physical access to the device and the ability to remove or modify the M.2 SATA storage device. Notably, it does not require advanced skills such as soldering, specialized hardware, or complex reverse engineering. The implications are significant for organizations that handle sensitive data on thin clients, especially those that are returned, lost, resold, or disposed of without proper data destruction.
The vulnerability has been assigned a CVSS 3.1 score of 6.1, classified as Medium. This rating reflects the requirement for physical access, the low attack complexity, and the potential for high impact on data confidentiality and integrity. The researcher reported the issue to HP PSIRT on February 22, 2026, and HP indicated that a fix was in quality assurance, though no official bulletin or patch was available at the time of disclosure.
Organizations relying on HP ThinPro full-disk encryption should consider all devices outside their direct physical control as potentially compromised until HP releases a comprehensive security update. Enabling Secure Boot and setting a BIOS password may offer some deterrence but do not address the fundamental PCR measurement gap exploited by this attack.