CVE-2025-59323: CPSD CryptoPro Secure Disk for Bitlocker before v7.7.4 fails to validate the integrity of the DataStore, 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.
Security readout for executives and security teams
Plain-English summary
CryptoPro Secure Disk for BitLocker before version 7.7.4 does not verify the integrity of its sensitive configuration and cryptographic datastore. A locally positioned attacker could manipulate that data, potentially stopping the service or running code with high privileges. This creates serious integrity, confidentiality, and operational risks on affected Windows systems.
Executive priority
Prioritize remediation for affected endpoints where local access is broadly available or compromise is plausible. High-privilege code execution could turn an initial foothold into complete system compromise. Accelerated patching is warranted, although the supplied evidence does not show active exploitation.
Technical view
CVE-2025-59323 is a CWE-345 integrity-validation failure affecting the CPSD DataStore, described as a non-partitioned filesystem containing configuration and cryptographic details. Crafted contents may cause denial of service or high-privilege code execution. CVSS 3.1 rates it 8.4 with local access, low complexity, no privileges, and no user interaction.
Likely exposure
Exposure is limited to systems running CryptoPro Secure Disk for BitLocker earlier than 7.7.4. The CVSS vector indicates exploitation requires local access, so this is not described as directly network-reachable. Risk is greatest where untrusted users, compromised software, or other attackers can modify the DataStore.
Exploitation context
The supplied sources do not establish active exploitation, and the CVE is not listed as KEV in the bundle. Public references include Black Hat research, indicating technical disclosure, but the provided evidence does not confirm publicly available exploit tooling or attacks in the wild.
Researcher notes
The version boundary comes from the CVE title and description; structured affected-product fields are unspecified. The exact DataStore location, attacker write path, and vendor remediation details are not included in the bundle. Validate those details against current CPSD guidance before designing detection logic or declaring systems unaffected.
Mitigation direction
Inventory CryptoPro Secure Disk for BitLocker installations and identify versions earlier than 7.7.4.
Upgrade affected installations to version 7.7.4 or later after confirming current vendor guidance.
Restrict local access and prevent unauthorized modification of CPSD storage and configuration data.
Increase monitoring for unexpected CPSD failures, datastore changes, and high-privilege process activity.
Validation and detection
Confirm installed CPSD versions through approved asset inventory or endpoint-management records.
Verify upgraded systems report version 7.7.4 or later and operate normally.
Review file-integrity and endpoint telemetry for unexplained DataStore modifications.
Investigate CPSD service crashes or unusual privileged processes around suspected datastore changes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-345: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-345 · source CWE mapping
Insufficient Verification of Data Authenticity
Insufficient Verification of Data Authenticity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.