CVE-2025-59694: Entrust Nshield 5c Privilege Escalation

CVE-2025-59694 Overview

CVE-2025-59694 is a firmware vulnerability affecting the Chassis Management Board (CMB) in multiple Entrust nShield Hardware Security Module (HSM) products. This vulnerability allows a physically proximate attacker to persistently modify firmware and influence the insecurely configured appliance boot process. The attack requires either direct access to the JTAG interface or the ability to perform a firmware upgrade to the chassis management board, making it a physical access attack vector designated as "F03" by the researchers.

Hardware Security Modules are critical cryptographic devices used to safeguard digital keys and perform encryption operations in enterprise environments. A compromise at the firmware level of these devices poses significant risks to the integrity of cryptographic operations and the protection of sensitive key material.

Critical Impact

Physical attackers can persistently compromise HSM firmware integrity, potentially undermining the security guarantees these devices are designed to provide for cryptographic key protection.

Affected Products

• Entrust nShield Connect XC (Base, Mid, High variants) - firmware through version 13.6.11 or 13.7
• Entrust nShield 5c - firmware through version 13.6.11 or 13.7
• Entrust nShield HSMi - firmware through version 13.6.11 or 13.7

Discovery Timeline

• December 2, 2025 - CVE-2025-59694 published to NVD
• December 15, 2025 - Last updated in NVD database

Technical Details for CVE-2025-59694

Vulnerability Analysis

This vulnerability resides in the Chassis Management Board component of Entrust nShield HSM appliances. The CMB is responsible for low-level hardware management functions, including the boot process initialization. The security flaw stems from insufficient hardware verification mechanisms (CWE-1274: Improper Access Control for Volatile Memory Containing Boot Code), which allows unauthorized firmware modifications to persist across reboots.

The vulnerability has been assigned a CVSS 3.1 score of 6.8 (Medium) with the vector string CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. This rating reflects:

• Physical Attack Vector (AV:P): Requires physical proximity to the device
• Low Attack Complexity (AC:L): Once physical access is obtained, exploitation is straightforward
• No Privileges Required (PR:N): No authentication needed at the hardware level
• High Impact: Complete compromise of confidentiality, integrity, and availability

The EPSS (Exploit Prediction Scoring System) indicates a probability of 0.022% with a percentile of 5.24, suggesting relatively low likelihood of widespread exploitation in the wild, consistent with the physical access requirement.

Root Cause

The root cause of this vulnerability is improper access control for volatile memory containing boot code. The Chassis Management Board fails to adequately verify the integrity and authenticity of firmware during the boot process, allowing modified firmware to execute without detection. This represents a fundamental secure boot implementation weakness where:

1. The JTAG debug interface lacks sufficient access restrictions
2. Firmware upgrade mechanisms do not properly validate code authenticity
3. Boot-time integrity verification is insufficient or improperly configured

Attack Vector

Exploitation of CVE-2025-59694 requires physical access to the target HSM device. An attacker with such access can compromise the system through two primary methods:

Method 1 - JTAG Interface Attack:
The attacker connects to the JTAG debugging interface on the Chassis Management Board, which provides direct hardware-level access. Through this interface, the attacker can read, modify, and write firmware directly to the CMB's flash memory.

Method 2 - Malicious Firmware Upgrade:
The attacker performs a firmware upgrade to the chassis management board using modified firmware. Due to insufficient validation of firmware authenticity, the malicious firmware is accepted and installed.

In both scenarios, the modified firmware persists across device reboots, providing the attacker with persistent access and the ability to influence the HSM's boot process. This could potentially allow for key extraction, cryptographic operation manipulation, or complete device compromise.

For detailed technical information about this vulnerability, see the Google Security Research advisory.

Detection Methods for CVE-2025-59694

Indicators of Compromise

• Unexpected firmware version changes on the Chassis Management Board
• Evidence of physical tampering with HSM enclosure or JTAG access points
• Anomalous boot behavior or timing deviations during device startup
• Unexpected modifications to HSM configuration or security policies
• Tamper-evident seal breakage on device chassis

Detection Strategies

Physical Security Monitoring:
Organizations should implement comprehensive physical security monitoring for HSM devices, including video surveillance, access logging, and tamper-evident seals. Any unauthorized physical access should trigger immediate investigation.

Firmware Integrity Verification:
Regularly verify firmware versions and checksums against known-good values provided by Entrust. Document baseline firmware states and compare periodically to detect unauthorized modifications.

Boot Process Monitoring:
Monitor and log boot sequences where possible. Deviations from expected boot timing or behavior may indicate firmware tampering.

SentinelOne Singularity Platform:
While this vulnerability targets firmware-level components that operate below the operating system, SentinelOne's endpoint detection capabilities can identify anomalous behavior patterns that may result from a compromised HSM interacting with connected systems.

Monitoring Recommendations

1. Implement strict physical access controls with multi-person authorization for HSM access
2. Deploy environmental monitoring systems around HSM installations
3. Establish baseline firmware fingerprints and verify integrity on a scheduled basis
4. Monitor network traffic from HSM management interfaces for unusual patterns
5. Enable audit logging for all HSM administrative operations
6. Review tamper-evident mechanisms during regular security assessments

How to Mitigate CVE-2025-59694

Immediate Actions Required

• Verify current firmware versions on all affected Entrust nShield devices
• Review and strengthen physical access controls to HSM installations
• Inspect devices for evidence of physical tampering or JTAG access
• Document current firmware baselines for integrity verification
• Contact Entrust support for guidance on securing affected devices

Patch Information

Organizations should monitor Entrust's official security advisories for firmware updates that address this vulnerability. The affected firmware versions include those through 13.6.11 and version 13.7. Contact Entrust directly for remediation guidance and updated firmware availability.

Key resources:

• Entrust HSM Product Information
• Google Security Research Advisory

Workarounds

Until a patch is available, organizations should implement the following compensating controls:

Physical Security Hardening:
Ensure HSM devices are installed in physically secured environments with restricted access. Implement multi-person authorization for any physical access to HSM equipment. Deploy tamper-evident seals and verify their integrity regularly.

JTAG Interface Protection:
Where possible, disable or physically obstruct JTAG interfaces. Some organizations may consider epoxy or physical barriers over debug interfaces, though this should be evaluated against warranty and support implications.

Firmware Upgrade Controls:
Implement strict change management procedures for any firmware modifications. Require cryptographic verification of firmware packages before installation and maintain secure audit trails of all firmware-related activities.

Network Isolation:
Ensure HSM management interfaces are isolated on dedicated management networks with strict access controls. Monitor all traffic to and from HSM devices for anomalies.