dbcve.org
Junos SpaceApplication · Juniper

CVE-2025-59975

HIGH · 7.5 CVSS v3.1 Published 2025-10-09
Fix available
A fix is available. Upgrade to 22.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
An Uncontrolled Resource Consumption vulnerability in the HTTP daemon (httpd) of Juniper Networks Junos Space allows an unauthenticated network-based attacker flooding the device with inbound API calls to consume all resources on the system, leading to a Denial of Service (DoS). After continuously flooding the system with inbound connection requests, all available file handles become consumed, blocking access to the system via SSH and the web user interface (WebUI), resulting in a management interface DoS. A manual reboot of the system is required to restore functionality. This issue affects Junos Space: * all versions before 22.2R1 Patch V3, * from 23.1 before 23.1R1 Patch V3.

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 · moderate confidence

An uncontrolled resource consumption vulnerability exists in the HTTP daemon (httpd) of Juniper Networks Junos Space. An unauthenticated remote attacker can flood the device with inbound API calls, consuming all available file handles on the system. This exhausts system resources, blocking both SSH and web UI access, resulting in a management interface DoS that requires a manual reboot to recover.

MitigationApply the vendor-supplied patches (22.2R1 Patch V3 or 23.1R1 Patch V3 depending on your current branch). As compensating controls, implement network-level rate limiting or DDoS protection to limit inbound connection requests to the management interface.

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
Junos SpaceApplication
Affected:< 22.2= 22.2= 23.1

CVSS 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
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Junos Space version
    Run 'show version' from the Junos Space CLI or check the web UI under Administration > System > Software. Alternatively, query the API endpoint /api/space/system-management/health/system-information
    Affected if The installed version is < 22.2, or exactly 22.2, or exactly 23.1 (unpatched)
  2. Confirm patch installation status
    In the web UI, navigate to Administration > System > Software and view the Applied Patches column. Check if 22.2R1 Patch V3 or 23.1R1 Patch V3 is installed for your respective branch
    Affected if No patch or an earlier patch version is installed (the vulnerability remains unmitigated)
  3. Verify httpd service exposure
    From an external host, attempt to reach the Junos Space management interface over HTTP/HTTPS (ports 443 or 8080). Confirm the httpd process is accessible without authentication
    Affected if The HTTP daemon is exposed to unauthenticated network traffic on the management interface
  4. Check for resource exhaustion indicators
    Access the device console directly (as console access may still work) and run 'show system resources' or 'lsof | wc -l' to count open file handles. Compare against expected baseline
    Affected if File handle count is near system limits (typically 65535), indicating potential exploitation in progress or recent attack

You are affected if your Junos Space version is unpatched and running any version before 22.2R1 Patch V3 or 23.1R1 Patch V3, and the management interface httpd is network-accessible to unauthenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 22.2 or later
Fixed in 22.2
Interim mitigation

Apply the vendor-supplied patches (22.2R1 Patch V3 or 23.1R1 Patch V3 depending on your current branch). As compensating controls, implement network-level rate limiting or DDoS protection to limit inbound connection requests to the management interface.

Recommended fix High confidence

22.2R1 Patch V3 or 23.1R1 Patch V3 (whichever applies to your current branch)

  1. Identify current Junos Space version using 'show version' or WebUI
  2. Contact Juniper Networks support portal (supportportal.juniper.net) to obtain the appropriate patch
  3. For versions < 22.2 or = 22.2: Obtain and apply patch 22.2R1 Patch V3
  4. For versions = 23.1: Obtain and apply patch 23.1R1 Patch V3
  5. Apply the patch following Juniper Networks standard patch deployment procedures for Junos Space
  6. After patch application, verify patch is installed via 'show version' or WebUI
  7. Test that HTTP service handles multiple connections without exhausting file handles
  8. Verify SSH and WebUI remain accessible after simulating multiple inbound connections
Caveat Patches may require maintenance window; always test in staging environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Junos Space Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59975 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59975 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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