Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain local/physical access to CPSD-protected endpoint
-
DeliveryPresent or craft LUKS-encrypted volume
-
ExploitFlawed validation skips all integrity checks
-
ExecutionModify protected boot/system files
-
ImpactTampered files trusted, evade detection
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Signature verification
|
| Exploitation Conditions | The concrete prerequisite from the description is that a LUKS-encrypted volume must be present/handled by the product - that specific condition is what makes CPSD fail its encryption validation and skip every CryptoPro file-integrity check. Exploitation therefore requires the affected component (CryptoPro Secure Disk for Bitlocker before v7.7.4) to be in use AND a LUKS encryption context to be reachable by the attacker; it is NOT a bypass that fires against a default BitLocker-only deployment with no LUKS involvement. Practically limiting factors: the attacker needs the ability to influence the encrypted-volume state on the target endpoint, which implies local/physical proximity despite the CVSS AV:N label, so this is not a mass-remote, unauthenticated internet-facing exploit against default configurations. |
| Impact | The signals conflict and must be weighed rather than taken at face value. The MITRE-supplied CVSS 3.1 vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/C:H/I:H/A:N, base 9.1) claims a remote, unauthenticated, network attack - but the described defect is an integrity-verification bypass in a full-disk-encryption product, which in practice is exercised by an actor with local or physical access to the endpoint (a classic evil-maid / tamper scenario), not over a network. This AV:N-vs-local-nature discrepancy should be verified with the vendor; treated as network-remote the score is inflated. Countervailing signals point to lower urgency: EPSS is 0.11% (1st percentile), it is NOT on CISA KEV, and no weaponized exploit is public - only a Black Hat research disclosure. The realistic impact is high for the specific integrity guarantee (an attacker who can touch the disk can plant tampered files that evade detection), but the addressable population is small and exploitation is not automatable at scale. Organizations running this exact product for compliance-driven endpoint integrity should still patch promptly, since the flaw negates the core assurance they bought the product for; even a mid-sized municipal IT team in kielce running these encrypted endpoints should schedule the 7.7.4 upgrade rather than defer it, but for everyone else this is a low-prevalence, low-probability item rather than an emergency. |
| Exploit ScenarioDerived | An attacker who gains brief physical or local access to a laptop protected by CryptoPro Secure Disk for Bitlocker attaches or crafts a LUKS-encrypted volume so the product's flawed detection engages, which causes CPSD to skip all file-integrity checks. The attacker then modifies protected system or boot files (e.g., planting a backdoored binary), and because integrity verification is bypassed the tampering is not detected on subsequent boot. No public exploit code exists yet; the technique is described in a Black Hat USA 2026 research presentation. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 13, 2026
Integrity-check bypass in CPSD CryptoPro Secure Disk for Bitlocker before v7.7.4 lets an attacker defeat the product's file-integrity verification: when a LUKS-encrypted volume is present, the software fails to validate that encryption correctly and then silently skips ALL CryptoPro integrity checks, so tampered files pass as trusted. This undermines the pre-boot/endpoint trust guarantees the product exists to provide, enabling evil-maid-style tampering. There is no public exploit identified at time of analysis, though the flaw is the subject of a Black Hat USA 2026 disclosure ('The Cost of Obscurity'); EPSS is very low (0.11%, 1st percentile) and it is not on CISA KEV.
RemediationAI
Primary fix: upgrade to CryptoPro Secure Disk for Bitlocker v7.7.4 or later (Vendor-released patch: v7.7.4), which is the version at which the LUKS-validation/integrity-skip defect is resolved; consult the vendor at https://www.cpsd.at/blog/ for release notes and https://nvd.nist.gov/vuln/detail/CVE-2025-59324 for the tracking record. Until patched, the meaningful compensating controls are physical and access-based rather than network: restrict and monitor physical access to endpoints running the product (locked enclosures, tamper-evident seals, secured boot order/BIOS passwords) so an attacker cannot present or manipulate a LUKS volume to trigger the integrity-check skip, and where feasible avoid LUKS-encrypted volume configurations on affected hosts since it is the presence of LUKS that triggers the bypass - the trade-off being reduced flexibility for mixed Linux/BitLocker fleets. Independently re-attest endpoint file integrity via an out-of-band mechanism (e.g., TPM measured boot / external integrity tooling) so you are not relying solely on CPSD's checks while unpatched.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
CryptoPro Secure Disk for Bitlocker (CPSD, an Austrian vendor - cpsd.at) is a pre-boot authentication and endpoint full-disk-encryption management layer that wraps Microsoft BitLocker and can interoperate with LUKS (the Linux Unified Key Setup) encrypted volumes. The root cause maps to CWE-347 (Improper Verification of Cryptographic Signature): the product's integrity subsystem is supposed to cryptographically verify protected files, but the logic that detects LUKS encryption is flawed such that the mere presence of encryption causes the entire integrity-verification path to be short-circuited. In other words, an attribute an attacker can influence (encryption being 'present') acts as an implicit trust bypass rather than an additional control, so signed/measured integrity checks that should gate boot or file trust are never enforced. The provided CPE string (cpe:2.3:a:n/a:n/a:*) is a placeholder and carries no real product/version data.
Know when Jwt Attack gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Integrity-check bypass on a disk-encryption product realistically needs local/physical access (AV:L) with no credentials (PR:N); impact is defeated file integrity (I:H), not confidentiality or availability.
Primary rating from Vendor (mitre).
CVSS VectorVendor: mitre
Lifecycle Timeline
3DescriptionCVE.org
CPSD CryptoPro Secure Disk for Bitlocker before v7.7.4 fails to properly validate LUKS encryption and, if encryption is present, all CryptoPro file integrity checks are skipped.
Executive ViewAI
CPSD CryptoPro Secure Disk for Bitlocker versions before 7.7.4 contain a critical integrity-check bypass with no public exploit identified at time of analysis; the flaw permits attackers to tamper with encrypted files while evading product-level detection. When LUKS-encrypted volumes are present, the software silently disables all file-integrity verification, allowing modified files to pass as trusted. Organizations relying on this product for endpoint encryption assurance and compliance must immediately reassess their security posture and implement interim protective measures.
No vendor-released patch identified at time of analysis. Until CPSD releases v7.7.4 or later: (1) inventory and isolate systems running affected versions, prioritizing those with LUKS-encrypted volumes; (2) implement external host-based file-integrity monitoring (such as AIDE, OSSEC, or Samhain) to detect unauthorized modifications independent of CPSD; (3) enforce strict physical and logical access controls on affected systems; (4) deploy endpoint detection and response (EDR) tooling configured for tampering detection; (5) enable comprehensive audit logging with alerts for file modifications to protected directories; (6) for compliance-critical assets, prepare to migrate from CPSD integrity assurance to external verification solutions.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
More in Jwt Attack
View allWhy is Microsoft republishing a CVE from 2013? We are republishing CVE-2013-3900 in the Security Update Guide to update
Authentication bypass in SimpleHelp 5.5.15 and prior (plus 6.0 pre-release builds) allows remote unauthenticated attacke
Authentication bypass in WSO2 API Manager and related components (Universal Gateway, Traffic Manager, API Control Plane,
Authentication bypass in Fortinet FortiOS, FortiProxy, and FortiSwitchManager allows unauthenticated remote attackers to
ruby-saml provides security assertion markup language (SAML) single sign-on (SSO) for Ruby. Rated critical severity (CVS
Security feature bypass in Microsoft .NET (shipped via Visual Studio 2022 17.12/17.14 and Visual Studio 2026 18.7) lets
ruby-saml provides security assertion markup language (SAML) single sign-on (SSO) for Ruby. Rated critical severity (CVS
The package jsrsasign before 10.5.25 are vulnerable to Improper Verification of Cryptographic Signature when JWS or JWT
Authentication and authorization bypass in fast-jwt 6.2.0 through 6.2.4 (npm, NearForm) lets a remote, unauthenticated a
A library injection vulnerability exists in Microsoft Teams (work or school) 24046.2813.2770.1094 for macOS. Rated criti
A library injection vulnerability exists in the WebView.app helper app of Microsoft Teams (work or school) 24046.2813.27
A library injection vulnerability exists in the com.microsoft.teams2.modulehost.app helper app of Microsoft Teams (work
EUVD-2025-210713
GHSA-g8wr-64q9-3xm2
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB