Vulnerability in Juniper Security Director Policy Enforcer (CVE-2025-11198)
Summary
Vulnerability in Juniper Security Director Policy Enforcer (CVE-2025-11198). Data can be tampered with by attackers.
Original description
The description as published by the source.
A Missing Authentication for Critical Function vulnerability in Juniper Networks Security Director Policy Enforcer allows an unauthenticated, network-based attacker to replace legitimate vSRX images with malicious ones.
If a trusted user initiates deployment, Security Director Policy Enforcer will deliver the attacker's uploaded image to VMware NSX instead of a legitimate one.
This issue affects Security Director Policy Enforcer:
- All versions before 23.1R1 Hotpatch v3.
This issue does not affect Junos Space Security Director Insights.
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-11198 has been found in Juniper Security Director Policy Enforcer.
Data can be tampered with by attackers. CVSS score: 7.4/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Juniper Security Director Policy Enforcer CVE-2025-11198" on the vendor's site.
CVE-2025-11198 (Juniper Security Director Policy Enforcer) — CWE-306 / CVSS v3 7.4
Attack vector: remote (network-reachable) / unauthenticated
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.
A vulnerability (CWE-306) exists in Juniper Security Director Policy Enforcer.
Check the vendor advisory for the affected versions of Juniper Security Director Policy Enforcer.
Severity: High (CVSS 7.4/10). Data can be tampered with by attackers.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Juniper Security Director Policy Enforcer を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- patch sirt@juniper.net