CVE-2025-11198
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a Missing Authentication for Critical Function vulnerability in Juniper Security Director Policy Enforcer. An unauthenticated, network-based attacker can upload malicious vSRX virtual firewall images through the Policy Enforcer component. When a legitimate trusted user initiates a deployment, the attacker's malicious image is delivered to VMware NSX instead of the legitimate vSRX image, allowing compromise of the virtual firewall infrastructure.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 23.1= 23.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Juniper Security Director Policy Enforcer is installedLocate the Security Director installation and check the product version. This is typically found in the Security Director management console or through the system package management. Query the installed software components for 'Policy Enforcer' or 'Security Director'Affected if Policy Enforcer version is found to be < 23.1 or = 23.1 (exact version check required)
-
Verify the Policy Enforcer component versionAccess the Security Director admin interface or check the version through the product's built-in version display. Look for the Policy Enforcer module specifically, as Security Director may have multiple component versionsAffected if The Policy Enforcer component version is 23.1 or any version below 23.1
-
Confirm VMware NSX integration is configuredCheck the Policy Enforcer configuration for VMware NSX integration settings. This is typically found in the Policy Enforcer network settings or deployment configuration where vSRX images are specified for NSX deliveryAffected if NSX integration is enabled and Policy Enforcer is configured to deploy vSRX images to NSX
-
Inspect for unexpected or unauthorized vSRX image uploadsReview the Policy Enforcer image repository or deployment queue for any vSRX images that were not initiated by legitimate administrators. Check the image upload timestamps and sourceAffected if Unexpected vSRX images appear in the deployment queue or image repository that were not explicitly uploaded by trusted administrators
-
Review Policy Enforcer management access logsExamine the Policy Enforcer access and audit logs for unauthenticated or unauthorized API calls, particularly those related to image upload or deployment functionsAffected if Unauthenticated requests were accepted by Policy Enforcer for image upload or deployment configuration changes
A system is affected if Juniper Security Director Policy Enforcer version 23.1 or below is installed AND the Policy Enforcer component is actively configured to manage vSRX deployments to VMware NSX infrastructure.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped23.1
Apply Juniper Security Director Policy Enforcer version 23.1R1 Hotpatch v3 or later. If immediate patching is not possible, implement network segmentation and monitoring to restrict unauthorized access to the Policy Enforcer management interface.
23.1R1 Hotpatch v3
- Upgrade Security Director Policy Enforcer to version 23.1R1 Hotpatch v3 or later to remediate this vulnerability.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,440.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11198 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-11198 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data