CVE-2025-11198
Juniper · Juniper Networks Multiple Products
A critical vulnerability has been discovered in Juniper Networks Security Director Policy Enforcer, identified as CVE-2025-11198.
Executive summary
A critical vulnerability has been discovered in Juniper Networks Security Director Policy Enforcer, identified as CVE-2025-11198. This flaw allows an unauthenticated attacker on the network to replace legitimate virtual firewall (vSRX) images with malicious ones, potentially leading to a complete compromise of network security. Successful exploitation could result in data theft, network eavesdropping, and unauthorized access to the internal network.
Vulnerability
This vulnerability is a "Missing Authentication for Critical Function" (CWE-306). The Security Director Policy Enforcer contains a service responsible for managing and deploying vSRX images that fails to properly authenticate requests. An unauthenticated, network-based attacker can craft a malicious request to this service, instructing it to download and deploy a new vSRX image from an attacker-controlled server. Because the request is not authenticated, the system trusts it and replaces the legitimate, secure vSRX image with the attacker's malicious version, which could contain backdoors, packet sniffers, or other malware.
Business impact
This vulnerability is rated as High severity with a CVSS score of 7.4. Exploitation could have a severe and direct impact on business operations. Replacing a core network security component like a vSRX virtual firewall with a malicious version would effectively dismantle the network perimeter's defenses. This could lead to the interception and exfiltration of sensitive corporate or customer data, a complete loss of network segmentation, and provide an attacker with a persistent foothold for lateral movement within the corporate network. The potential consequences include major data breaches, significant business disruption, reputational damage, and regulatory penalties.
Remediation
Immediate Action: The primary and most effective remediation is to apply the security updates provided by Juniper Networks immediately. After patching, review system and access logs for any unauthorized vSRX image deployment activities that may have occurred prior to the update.
Proactive Monitoring:
- Log Analysis: Scrutinize logs from Juniper Security Director for any vSRX image update or deployment events originating from unknown or unauthorized IP addresses.
- Network Traffic Analysis: Monitor outbound network traffic from the Security Director Policy Enforcer for connections to suspicious or non-standard IP addresses or domains, which could indicate the download of a malicious image.
- File Integrity Monitoring: Implement file integrity checks on the stored vSRX images. Validate the file hashes of currently deployed vSRX instances against the official hashes published by Juniper to detect any unauthorized modifications.
Compensating Controls: If immediate patching is not feasible, implement the following controls to reduce risk:
- Access Control Lists (ACLs): Strictly limit network access to the management interface of the Security Director Policy Enforcer. Only allow connections from a dedicated and secured management subnet or specific administrative hosts.
- Egress Filtering: Apply strict firewall rules to control outbound traffic from the Policy Enforcer, blocking it from establishing connections to untrusted external destinations on the internet. This can prevent the download of a malicious image.
Exploitation status
Public Exploit Available: false
Analyst recommendation
Due to the high severity (CVSS 7.4) and the critical function of the affected software, we strongly recommend that organizations prioritize the immediate patching of CVE-2025-11198. An unauthenticated attacker can leverage this flaw to gain complete control over a core security appliance, posing a direct threat to the entire network. Although this vulnerability is not currently listed on the CISA KEV list, its characteristics make it a prime candidate for future inclusion. All affected Juniper assets should be identified and remediated without delay.