CVE-2025-59694
Entrust Nshield 5C Firmware ≤ 13.6.12
Raw vector
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2025-59694 is a medium-severity Improper Access Control for Volatile Memory Containing Boot Code (CWE-1274) vulnerability in Entrust Nshield 5C Firmware. Its CVSS base score is 6.8 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Component Firmware (T1542.002); ranked at the 19th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to PE-3 (Physical Access Control) and SA-18 (Tamper Resistance and Detection) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-200260
Vulnerability Data
The Chassis Management Board in Entrust nShield Connect XC, nShield 5c, and nShield HSMi through 13.6.11, or 13.7, allows a physically proximate attacker to persistently modify firmware and influence the (insecurely configured) appliance boot process. To exploit this, the attacker…
more
must modify the firmware via JTAG or perform an upgrade to the chassis management board firmware. This is called F03.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Vulnerability enables persistent, undetectable firmware modification on chassis management board via JTAG/upgrade, facilitating component firmware alteration for pre-OS boot control/persistence (T1542.002), inhibiting system recovery (T1490), disabling/modifying tamper defenses (T1562.001), and spoofing tamper events/LCD alerts (T1562.011).
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
Mitigating Controls (NIST 800-53 r5) AI
Directly blocks physically proximate attackers from reaching the chassis board to perform JTAG or firmware modifications.
Requires tamper-resistance mechanisms on hardware components to stop unauthorized firmware changes via physical interfaces such as JTAG.
Enforces cryptographic verification of firmware integrity before boot, mitigating the insecure boot-process configuration described in the CVE.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
PR.DS-10 directly requires protecting data-in-use (including VM) from unauthorized access, eliminating most of this specific boot-code exposure, yet the weakness also spans secure-boot process design and NVM-to-VM transfer that one general data-protection outcome does not fully close.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Logging can detect unauthorized writes to volatile memory but does not prevent the weakness.
Restricting privileged utilities reduces the chance of tampering with boot code in volatile memory.
Privileged access rights can limit who or what can write to volatile memory used for boot code.
Secure system architecture principles include memory protection mechanisms that can mitigate this weakness.
Information access restriction directly addresses unauthorized access to volatile memory holding boot code.