CVE-2025-59705

Executive Summary

CVE-2025-59705 is a critical physical security vulnerability affecting Entrust nShield hardware security modules (HSMs), specifically the nShield Connect XC, nShield 5c, and nShield HSMi series. The flaw, dubbed "Unauthorized Reactivation of the USB interface" (F01), allows a physically proximate attacker to escalate privileges by enabling the USB interface through chassis probe insertion during system boot. This bypasses the intended security posture of the HSM, which typically disables the USB interface to prevent unauthorized data extraction or firmware manipulation.

The vulnerability is rooted in the hardware design and boot process, where the USB interface can be reactivated by physically probing the chassis during the boot sequence. This grants an attacker with physical access the ability to connect USB devices, potentially leading to privilege escalation, data exfiltration, or installation of malicious firmware. The CVSS score is 0.0 due to lack of official scoring, but based on the vector, the actual severity is high (7.6) given the physical access requirement but high impact on confidentiality, integrity, and availability.

Key Risk: Physical access to the HSM chassis during boot allows USB reactivation, bypassing security controls.

Supply Chain & Package Security

This vulnerability is not related to software supply chain packages (NPM, PyPI, Go, Ruby). It is a hardware-level flaw in Entrust nShield HSMs. Organizations using these devices should verify the physical security of their data centers and ensure that only authorized personnel have access to the hardware.

CVSS Breakdown & Threat Level

CVSS Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

• Attack Vector (AV): Physical (P) – The attacker must have physical access to the device.
• Attack Complexity (AC): Low (L) – The attack requires simple chassis probing during boot.
• Privileges Required (PR): None (N) – No prior privileges needed.
• User Interaction (UI): None (N) – No user action required.
• Scope (S): Unchanged (U) – The vulnerability affects only the HSM.
• Confidentiality (C): High (H) – Potential for data exfiltration.
• Integrity (I): High (H) – Potential for firmware modification.
• Availability (A): High (H) – Potential for denial of service or device compromise.

Threat Level: High (7.6) – Requires physical access but has severe consequences.

Deep Dive & Mechanics

The vulnerability lies in the boot process of Entrust nShield HSMs. During system boot, the USB interface is typically disabled to prevent unauthorized access. However, by inserting a probe into the chassis (e.g., using a conductive tool to short specific pins or trigger a hardware reset), an attacker can reactivate the USB interface before the operating system fully loads. This allows the attacker to connect a USB device (e.g., a keyboard, storage device, or malicious HID device) to the HSM.

Technical Details:

• The boot sequence checks for chassis intrusion or tamper events, but the probe insertion bypasses this check.
• Once USB is enabled, the attacker can interact with the HSM's bootloader or firmware, potentially loading a custom firmware or extracting cryptographic keys.
• The attack requires precise timing during the boot process, but no specialized tools beyond a simple probe (e.g., a paperclip or multimeter probe).

Root Cause: Inadequate hardware-level protection of the USB interface during the boot phase, allowing physical manipulation to override security policies.

Vulnerable vs. Patched Code

This is a hardware vulnerability, so there is no traditional code diff. However, the following describes the vulnerable vs. patched behavior:

Vulnerable Behavior:

• During boot, the USB interface is disabled by software, but hardware pins controlling USB power or data lines can be manipulated via chassis probes.
• The bootloader does not enforce a tamper-resistant check for USB reactivation.

Patched Behavior (Expected):

• Hardware-level fuses or tamper switches that physically disable USB lines during boot, preventing reactivation even with probes.
• Firmware update that locks USB configuration in a secure enclave, requiring cryptographic authentication to enable.

No code snippet available for this hardware vulnerability.

Exploitation & Lab Setup

Red Team (Exploitation)

Prerequisites:

• Physical access to the target Entrust nShield HSM (nShield Connect XC, nShield 5c, or nShield HSMi).
• A conductive probe (e.g., a paperclip or multimeter probe).
• A USB device (e.g., a USB flash drive or a USB keyboard).

Exploitation Steps:

1. Power on the HSM or trigger a reboot.
2. During the boot process (typically within the first 10-30 seconds), insert the probe into the chassis to short specific pins (e.g., USB power enable or data line test points). The exact pin locations are not publicly documented but can be identified through hardware reverse engineering.
3. The USB interface becomes active. Connect a USB device.
4. If using a USB keyboard, press a key to interrupt the boot process (e.g., enter the bootloader menu).
5. Load a custom firmware or extract sensitive data from the HSM's storage.

Example (Conceptual):

# No public exploit code available. This is a hardware attack.
# Steps:
# 1. Identify USB test points on the HSM motherboard.
# 2. Short the USB_ENABLE pin to VCC during boot.
# 3. Connect USB device.

Blue Team (Defense)

Detection and Prevention:

• Physical Security: Restrict access to HSM devices to authorized personnel only. Use locked racks and CCTV monitoring.
• Tamper Detection: Enable chassis intrusion detection if available. Monitor for physical tampering alerts.
• Boot Monitoring: Implement boot-time integrity checks (e.g., TPM measurements) to detect unauthorized USB activation.
• Firmware Updates: Apply any patches from Entrust as soon as available. Currently, no patch exists, so physical controls are critical.

Hunting:

• Check HSM logs for unexpected USB device connections or boot interruptions.
• Monitor for physical access logs (e.g., badge access to server rooms) during boot events.

Indicators of Compromise (IOCs)

• Physical: Unauthorized USB devices connected to the HSM (e.g., flash drives, keyboards).
• Logs: HSM system logs showing USB device enumeration during boot (e.g., usb 1-1: new high-speed USB device number 2).
• Firmware: Unexpected firmware version or hash mismatch.
• Network: Unusual outbound connections from the HSM (if data exfiltration occurs).

Example IOC (Log Entry):

[Boot] USB controller enabled at 0x12345678
[Boot] New USB device found: vendor=0x0781, product=0x5583

Detection Engineering

YARA Rule

rule CVE_2025_59705_HSM_USB_Reactivation {
    meta:
        description = "Detects log entries indicating USB reactivation on Entrust nShield HSM"
        author = "Valters IT"
        date = "2025-04-10"
        reference = "CVE-2025-59705"
    strings:
        $usb_enable = "USB controller enabled" nocase
        $usb_device = "New USB device found" nocase
        $boot_phase = "Boot" nocase
    condition:
        all of them
}

Sigma Rule

title: Entrust nShield HSM USB Reactivation Detection
id: 8a9b7c6d-5e4f-3a2b-1c0d-9e8f7a6b5c4d
status: experimental
description: Detects log entries indicating unauthorized USB reactivation on Entrust nShield HSM during boot.
author: Valters IT
date: 2025-04-10
references:
    - https://nvd.nist.gov/vuln/detail/CVE-2025-59705
logsource:
    product: entrust
    service: hsm
detection:
    selection:
        - "USB controller enabled"
        - "New USB device found"
    condition: selection
falsepositives:
    - Legitimate maintenance activities (rare)
level: high

Suricata Rule

alert tcp $HOME_NET any -> $EXTERNAL_NET any (msg:"CVE-2025-59705 - Entrust HSM USB Reactivation - Potential Data Exfiltration"; flow:to_server; content:"|55 53 42|"; distance:0; within:3; classtype:attempted-recon; sid:1000001; rev:1;)

Note: This rule is a placeholder for detecting USB-related traffic. Actual exploitation may not generate network traffic.

Remediation & Mitigation

Immediate Actions:

1. Physical Access Control: Ensure only authorized personnel have physical access to HSMs. Use locked cabinets and access logs.
2. Boot Monitoring: Implement physical tamper detection and monitor boot logs for USB events.
3. Firmware Updates: Contact Entrust for patches. As of now, no patch is available, so rely on physical controls.

Long-Term Fix:

• Entrust must release a firmware update that disables USB at the hardware level during boot, or implement cryptographic authentication for USB activation.
• Organizations should consider replacing vulnerable HSMs with newer models that have hardware-based USB disablement.

Workaround:

• Disable USB ports physically (e.g., epoxy or remove USB connectors) if not needed for legitimate operations.

Valters IT