Search Results (6 CVEs found)

CVE Vendors Products Updated CVSS v3.1
CVE-2025-59325 1 Cpsd 1 Cryptopro Secure Disk 2026-08-13 N/A
CPSD CryptoPro Secure Disk for Bitlocker before v7.7.4 fails to encrypt the initramfs contents, allowing for the offline recovery of secrets and cryptographic details.
CVE-2025-59327 1 Cpsd 1 Cryptopro Secure Disk 2026-08-13 N/A
In CPSD CryptoPro Secure Disk for Bitlocker before v7.7.4, bootxsa.efi fails to properly validate LUKS encryption and, if encryption is present, all CryptoPro file integrity checks are skipped.
CVE-2025-59319 1 Cpsd 1 Cryptopro Secure Disk 2026-08-12 7.2 High
CPSD CryptoPro Secure Disk for Bitlocker before v7.7.4 fails to certify the integrity of the intended boot partition and selects the first partition index matching a hardcoded type value. A crafted Linux partition could be inserted ahead of this intended target, allowing for code execution in the context of high privilege.
CVE-2025-59320 1 Cpsd 1 Cryptopro Secure Disk 2026-08-12 4.6 Medium
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.
CVE-2025-59323 1 Cpsd 1 Cryptopro Secure Disk 2026-08-12 N/A
CPSD CryptoPro Secure Disk for Bitlocker before v7.7.4 fails to validate the integrity of the DataStore, a non-partitioned filesystem, responsible for storing configuration and cryptographic details. Crafted DataStore contents can impact service availability and/or allow for code execution in the context of high privilege.
CVE-2025-10010 2 Cpsd, Cpsd It Services 2 Cryptopro Secure Disk, Cryptopro Secure Disk For Bitlocker 2026-03-13 6.8 Medium
The CPSD CryptoPro Secure Disk application boots a small Linux operating system to perform user authentication before using BitLocker to decrypt the Windows partition. The system is located on a separate unencrypted partition which can be reached by anyone with access to the hard disk. Multiple checks are performed to validate the integrity of the Linux operating system and the CryptoPro Secure Disk application files. When files are changed an error is shown on system start. One of the checks is the Linux kernel's Integrity Measurement Architecture (IMA). It was identified that configuration files are not validated by the IMA and can then (if not checked by other measures) be changed. This allows an attacker to execute arbitrary code in the context of the root user and enables an attacker to e.g., plant a backdoor and access data during execution.