Categories
CVE-2025-59705 medium CVSS 6.8

Privilege Escalation in Entrust (CVE-2025-59705)

Summary

Vulnerability in Entrust (CVE-2025-59705). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 13.6.12 or later.

Original description

The description as published by the source.

Entrust nShield Connect XC, nShield 5c, and nShield HSMi through 13.6.11, or 13.7 (patched in 13.6.12 (LTS) and 13.9.0 (STS)), allow a Physically Proximate Attacker to Escalate Privileges by enabling the USB interface through chassis probe insertion during system boot, aka "Unauthorized Reactivation of the USB interface" or F01.

Source: NIST National Vulnerability Database NVD

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2025-59705 has been found in Entrust.
Successful exploitation can lead to full system takeover. CVSS score: 6.8/10.
What to do: upgrade Entrust to 13.6.12 or later.
If unsure, ask your IT team or search "Entrust CVE-2025-59705" on the vendor's site.

CVE-2025-59705 (Entrust) — CWE-269 / CVSS v3 6.8
Attack vector: physical / unauthenticated / no user interaction
Patched: 13.6.12 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-269) exists in Entrust.

📍 Affected scope

Check the vendor advisory for the affected versions of Entrust.

🔥 Severity

Severity: Medium (CVSS 6.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 13.6.12.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Entrust' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'Entrust' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で Entrust を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade Entrust to 13.6.12

    ステージング環境で 13.6.12 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details