CVE-2025-59698
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-59698 is a medium-severity Generation of Incorrect Security Tokens (CWE-1270) vulnerability in Entrust Nshield 5C Firmware. Its CVSS base score is 6.8 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique System Firmware (T1542.001); 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-200256
Vulnerability Data
Entrust nShield Connect XC, nShield 5c, and nShield HSMi through 13.6.11, or 13.7, might allow a physically proximate attacker to gain access to the EOL legacy bootloader.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Vulnerabilities enable physical access to legacy bootloader, unprotected boot chain, firmware modification via JTAG or upgrades, and tamper log editing on EEPROM without traces or events, facilitating pre-OS boot persistence via system/component firmware changes and indicator removal.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly enforces physical access restrictions to hardware devices such as HSMs, blocking proximate attackers from reaching the legacy bootloader.
Requires tamper-resistance and detection mechanisms on components, directly addressing unauthorized physical access to the EOL bootloader.
Mandates removal or replacement of unsupported/EOL system components, eliminating the vulnerable legacy bootloader itself.
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.
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.
Security testing in development can detect incorrect token generation before deployment.
Proper use of cryptography ensures tokens are generated with correct algorithms, keys and entropy.
Secure development lifecycle practices include requirements and reviews that prevent flawed token-generation logic.
Application security requirements explicitly call for correct token issuance and validation mechanisms.
Secure coding standards reduce the likelihood of implementation errors that produce incorrect tokens.
Secure authentication mechanisms directly govern the correct generation and validation of security tokens.