dbcve.org
JunosOperating system · Juniper

CVE-2025-52964

MEDIUM · 6.5 CVSS v3.1 Published 2025-07-11
Fix available
A fix is available. Upgrade to 21.4 or later.
See remediation →
70/100
Remediation priority · Elevated
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
A Reachable Assertion vulnerability in the Routing Protocol Daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, network-based attacker to cause a Denial of Service (DoS). When the device receives a specific BGP UPDATE packet, the rpd crashes and restarts. Continuous receipt of this specific packet will cause a sustained DoS condition. For the issue to occur, BGP multipath with "pause-computation-during-churn" must be configured on the device, and the attacker must send the paths via a BGP UPDATE from a established BGP peer. This issue affects: Junos OS: * All versions before 21.4R3-S7, * from 22.3 before 22.3R3-S3, * from 22.4 before 22.4R3-S5, * from 23.2 before 23.2R2, * from 23.4 before 23.4R2. Junos OS Evolved: * All versions before 21.4R3-S7-EVO, * from 22.3 before 22.3R3-S3-EVO, * from 22.4 before 22.4R3-S5-EVO, * from 23.2 before 23.2R2-EVO, * from 23.4 before 23.4R2-EVO.

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 confidence

A reachable assertion in the Routing Protocol Daemon (rpd) causes a crash and restart when processing a specific BGP UPDATE packet. The attack requires the attacker to be an established BGP peer and the target device to have BGP multipath with 'pause-computation-during-churn' configured, resulting in a Denial of Service condition.

MitigationApply the vendor-supplied software updates for the affected Junos OS/Evolved versions. As a workaround, consider disabling the 'pause-computation-during-churn' feature if operationally feasible, or strictly control BGP peer access to trusted endpoints.

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
JunosOperating system
Affected:< 21.4= 21.4= 22.3= 22.4= 23.2= 23.4
Junos Os EvolvedOperating system
Affected:< 21.4= 21.4= 22.3= 22.4= 23.2= 23.4

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/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. Check Junos OS/Evolved version
    Run 'show version' or 'show version detail' and note the software version installed
    Affected if The version matches one of the affected ranges: < 21.4, = 21.4, = 22.3, = 22.4, = 23.2, or = 23.4
  2. Verify BGP is configured
    Run 'show configuration protocols bgp' to confirm BGP is enabled and has peer configurations
    Affected if BGP is not configured or no peers are defined - the vulnerability requires an established BGP peer relationship
  3. Confirm BGP multipath is enabled
    Run 'show configuration protocols bgp' and look for 'multipath' under the BGP configuration or peer/group level
    Affected if The 'multipath' option is not present in the BGP configuration - the flaw requires multipath to be enabled
  4. Check for pause-computation-during-churn setting
    Run 'show configuration protocols bgp' and search for the 'pause-computation-during-churn' option under the multipath hierarchy
    Affected if The 'pause-computation-during-churn' feature is explicitly configured under the BGP multipath settings - this is the specific configuration that enables the attack surface

A device is affected if it runs a Junos version in the specified list AND has an established BGP peer AND has BGP multipath enabled AND has the 'pause-computation-during-churn' feature configured, allowing a malicious BGP peer to trigger the assertion and cause a crash/restart loop.

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 21.4 or later
Fixed in 21.4
Interim mitigation

Apply the vendor-supplied software updates for the affected Junos OS/Evolved versions. As a workaround, consider disabling the 'pause-computation-during-churn' feature if operationally feasible, or strictly control BGP peer access to trusted endpoints.

Recommended fix High confidence

21.4R3-S7 / 22.3R3-S3 / 22.4R3-S5 / 23.2R2 / 23.4R2 (or respective -EVO variants for Junos OS Evolved)

  1. 1. Identify the current Junos OS or Junos OS Evolved version running on the device using 'show version'
  2. 2. Determine which version branch (21.4, 22.3, 22.4, 23.2, or 23.4) the device is currently running
  3. 3. For 21.4 branch: upgrade to 21.4R3-S7 or later (21.4R3-S7-EVO for Evolved)
  4. 4. For 22.3 branch: upgrade to 22.3R3-S3 or later (22.3R3-S3-EVO for Evolved)
  5. 5. For 22.4 branch: upgrade to 22.4R3-S5 or later (22.4R3-S5-EVO for Evolved)
  6. 6. For 23.2 branch: upgrade to 23.2R2 or later (23.2R2-EVO for Evolved)
  7. 7. For 23.4 branch: upgrade to 23.4R2 or later (23.4R2-EVO for Evolved)
  8. 8. If running a version not listed in affected versions, verify exact version is not vulnerable before proceeding
Caveat Standard Junos upgrade considerations apply - review release notes for any configuration changes or hardware compatibility. S variants are maintenance releases typically safe for upgrades.

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

Fix this in Junos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-52964 — 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-52964 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