Security readout for executives and security teams
Plain-English summary
CryptoPro Secure Disk for BitLocker before version 7.7.4 may trust the wrong boot partition. An attacker who already has high privileges could place a crafted Linux partition before the intended partition, causing privileged attacker-controlled code to run. Successful exploitation could compromise confidentiality, integrity, and availability.
Executive priority
Treat as a high-priority hardening and upgrade issue on affected endpoints. Immediate emergency action is not supported by current exploitation evidence, but privileged code execution could cause complete system compromise. Accelerate inventory and remediation wherever administrators, compromised privileged accounts, or management tooling can alter partitions.
Technical view
The product identifies the boot target by selecting the first partition whose type matches a hardcoded value, without certifying that partition is the intended trusted target. A crafted Linux partition positioned earlier can therefore be selected and execute code with high privilege. CVSS 3.1 rates this 7.2: network-accessible, low complexity, high privileges required, and no user interaction.
Likely exposure
Exposure is limited to deployments running CryptoPro Secure Disk for BitLocker versions earlier than 7.7.4. Risk is greatest where a privileged attacker can alter disk partition layout. The supplied affected-product metadata is incomplete, so organizations should confirm precise platform and version applicability with CPSD.
Exploitation context
The supplied record is not in CISA KEV and provides no evidence of active exploitation. Exploitation requires high privileges but can yield high-impact privileged code execution without user interaction. Public Black Hat presentation materials discuss the research; the bundle does not establish weaponized exploit availability.
Researcher notes
The core issue is inadequate boot-partition identity validation combined with first-match selection using a hardcoded partition type. The CVSS vector requires high privileges despite network attack-vector scoring. CWE-290 is assigned. Product metadata contains placeholders, and the bundle does not document affected operating systems, attack prerequisites beyond privileges, patch internals, or exploitation telemetry.
Mitigation direction
- Inventory CryptoPro Secure Disk for BitLocker installations and identify versions earlier than 7.7.4.
- Prioritize upgrading affected systems to version 7.7.4 or later, subject to CPSD guidance.
- Restrict privileged access capable of modifying disk partitions or boot configuration.
- Review CPSD guidance for additional mitigations, deployment prerequisites, and supported upgrade paths.
Validation and detection
- Confirm installed product versions through trusted software inventory records.
- Verify upgraded systems report version 7.7.4 or later.
- Inspect partition layouts for unexpected Linux partitions preceding the intended boot target.
- Confirm boot and encryption workflows operate correctly after remediation.
- Recheck CPSD guidance for clarified affected configurations or validation procedures.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-290: 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.
Open ATT&CK lookupExecution behavior lookup
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.
Open ATT&CK lookupCVE-2025-59319 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H1.25.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
7.2HighVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.cpsd.at/blog/CVE reference, mitre
- https://i.blackhat.com/BH-USA-26/Presentations/US-26-Burch-The-Cost-of-Obscurity-Wednesday.pdfCVE reference, mitre
- https://i.blackhat.com/BH-USA-26/Presentations/US-26-Burch-The-Cost-of-Obscurity-wp.pdfCVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authentication Bypass by Spoofing
Authentication Bypass by Spoofing represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.