CVE-2025-59321 in Secure Disk for BitLocker
Summary
by MITRE • 08/12/2026
CPSD CryptoPro Secure Disk for Bitlocker before v7.7.4 contains a default TPM PCR policy that fails to consider the system boot state. This allows the TPM to be unsealed via an unintended execution path or from another hardware platform.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Analysis
by VulDB Data Team • 08/12/2026
The vulnerability in CPSD CryptoPro Secure Disk for BitLocker versions prior to v7.7.4 represents a critical flaw in the Trusted Platform Module implementation that undermines the fundamental security assumptions of the system. This issue stems from a default TPM PCR policy that inadequately accounts for the system boot state, creating a pathway for unauthorized access that bypasses intended security controls. The flaw specifically affects how the TPM evaluates the integrity of the boot process and validates the trust chain that should prevent unauthorized key access.
The technical implementation fails to properly incorporate runtime measurements of the system boot sequence into the PCR policy validation mechanism. This oversight allows an attacker to potentially unseal encrypted data through unintended execution paths or by transferring the TPM state to different hardware platforms where the same policy would be considered valid. The vulnerability essentially permits a form of credential migration that should be impossible within a properly configured secure environment, creating opportunities for attackers to exploit the system through methods that circumvent the intended boot integrity checks.
From an operational perspective, this vulnerability exposes systems to significant risk as it enables potential attackers to gain access to encrypted data without proper authentication or validation of the boot environment. The impact extends beyond simple data compromise to potentially allow attackers to bypass full disk encryption protections entirely, particularly in environments where BitLocker is used alongside CryptoPro Secure Disk for comprehensive system security. This weakness can be exploited across different hardware platforms, making it especially dangerous in heterogeneous computing environments.
The flaw aligns with CWE-327, which addresses the use of weak cryptographic algorithms and improper implementation of cryptographic protocols, specifically targeting the inadequate handling of trust relationships within the TPM framework. From an ATT&CK perspective, this vulnerability maps to techniques involving privilege escalation and credential access through manipulation of system integrity checks, particularly T1552.1 for credentials from password storage providers and T1068 for exploit for local privilege escalation.
Mitigation strategies should focus on updating to version 7.7.4 or later where the TPM PCR policy has been properly enhanced to consider system boot state validation. Organizations must also implement comprehensive monitoring of TPM state changes and establish strict policies regarding hardware platform usage for encrypted systems. Additional protective measures include enabling proper audit logging of TPM operations and implementing network-based controls to detect unauthorized attempts to access or transfer TPM states between platforms. Regular security assessments should verify that the updated TPM policies are properly enforced and that no legacy configurations remain in place that could reintroduce this vulnerability through misconfiguration.