EUVD-2025-210715
GHSA-v2j8-qhjm-8g37
Severity by source
AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Physical disk access is the mandatory vector (AV:P); secrets readable below OS layer require no credentials (PR:N); full confidentiality loss via BitLocker decryption (C:H); no integrity or availability impact.
Primary rating from Vendor (mitre).
CVSS VectorVendor: mitre
Lifecycle Timeline
3DescriptionCVE.org
CPSD CryptoPro Secure Disk for Bitlocker before v7.7.4 stores TPM2.0 secrets in a serialized format within unused disk sectors. An unauthenticated attacker with physical access to the system disk can recover this information and craft an environment to unseal the TPM.
AnalysisAI
CryptoPro Secure Disk for BitLocker versions before v7.7.4 leaks TPM2.0 unsealing secrets by persisting them in a serialized binary format within unused disk sectors - raw storage areas that survive reboots and are accessible without operating system authentication. An unauthenticated attacker with physical access to the drive can image these sectors, extract the serialized secrets, and reconstruct a compatible TPM environment to unseal the BitLocker volume, effectively defeating the hardware-backed disk encryption the product is designed to enforce. No public exploit code has been identified at time of analysis; CISA SSVC rates exploitation as 'none', but the attack's low complexity once physical access is obtained was detailed publicly in a Black Hat USA 2026 research presentation, materially lowering the skill barrier for motivated actors.
Technical ContextAI
CryptoPro Secure Disk for BitLocker is a pre-boot authentication and disk encryption management solution that integrates with Microsoft BitLocker and the TPM 2.0 (Trusted Platform Module) hardware security subsystem. TPM 2.0 is designed to seal cryptographic keys against platform state measurements (PCR values), releasing them only when the system boots into an expected, unmodified configuration - the core trust anchor for BitLocker's hardware-backed encryption model. The root cause is CWE-922 (Insecure Storage of Sensitive Information): the software caches or persists TPM2.0 secrets - likely authorization values, primary seed derivatives, or sealed key blobs - in slack or unallocated disk sectors that sit outside any active filesystem partition. Because these sectors are not managed by the OS and are not encrypted independently, they are readable via forensic imaging or raw block-device access tools without requiring any credentials or elevated OS privileges. The serialized format implies structured binary data that can be parsed offline to reconstruct the unsealing material. The CPE data in the NVD entry is unpopulated (n/a), indicating the product is not formally indexed in the Common Platform Enumeration dictionary, which limits automated vulnerability scanner detection.
RemediationAI
Upgrade to CPSD CryptoPro Secure Disk for BitLocker v7.7.4 or later, which is the vendor-confirmed fix boundary per the CVE description. Organizations should consult the vendor advisory at https://www.cpsd.at/blog/ for upgrade procedures and any post-upgrade remediation steps - critically, after patching, affected systems should be assessed to determine whether previously stored secrets in unallocated disk sectors need to be explicitly overwritten, as patching the software does not automatically scrub data already written to slack space. Where immediate patching is not possible, enforce strict physical security controls: store affected endpoints in secure, access-logged facilities, implement device tracking and remote wipe policies for portable systems, and enforce full-disk BitLocker PIN or passphrase in addition to TPM sealing to raise the bar for unsealing even if disk secrets are recovered. Disk sector sanitization (secure erase or cryptographic wipe of unallocated space) on affected systems is a compensating control but requires care to avoid disrupting active partitions. No workaround eliminates the underlying data exposure without patching and sector remediation.
LibreNMS before 24.10.0 allows a remote attacker to execute arbitrary code via OS command injection involving AboutContr
Reachable assertion in Open5GS up to version 2.7.6 allows remote unauthenticated attackers to crash the Diameter CER han
A Command Injection issue in the payload build page in BYOB (Build Your Own Botnet) 2.0 allows attackers to execute arbi
Denial of service in Open5GS 2.7.6 and earlier allows network-adjacent attackers with low-privilege Diameter Gx peer acc
Denial of service in Open5GS HSS (Home Subscriber Server) versions 2.7.0 through 2.7.6 is triggered remotely by manipula
Remote command injection in Control Web Panel allows unauthenticated attackers to execute arbitrary OS commands as root
LINQPad before 5.52.01 Pro edition is vulnerable to Unsafe Deserialization in LINQPad.AutoRefManager::PopulateFromCache(
Remote code execution in dash-uploader (Python package for Plotly Dash) versions 0.1.0 through 0.7.0a2 allows unauthenti
Command injection in LiteLLM 1.18.10 lets attackers who can configure MCP (Model Context Protocol) servers supply arbitr
SQL injection in AzuraCast's backup restore flow (versions up to and including 0.23.7) lets an attacker achieve privileg
Arbitrary file read in Yu AI Code Mother v4.3 lets anonymous, remote attackers retrieve files outside the intended previ
Remote code execution in APScheduler (all versions through 3.10.x and 4.0.0a5) is achievable when applications deseriali
Same weakness CWE-922 – Insecure Storage of Sensitive Information
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today