dbcve.org
JunosOperating system · Juniper

CVE-2025-60004

HIGH · 7.5 CVSS v3.1 Published 2025-10-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Improper Check for Unusual or Exceptional Conditions 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 an affected system receives a specific BGP EVPN update message over an established BGP session, this causes an rpd crash and restart. A BGP EVPN configuration is not necessary to be vulnerable. If peers are not configured to send BGP EVPN updates to a vulnerable device, then this issue can't occur. This issue affects iBGP and eBGP, over IPv4 and IPv6. This issue affects: Junos OS: * 23.4 versions from 23.4R2-S3 before 23.4R2-S5, * 24.2 versions from 24.2R2 before 24.2R2-S1, * 24.4 versions before 24.4R1-S3, 24.4R2; Junos OS Evolved: * 23.4-EVO versions from 23.4R2-S2-EVO before 23.4R2-S5-EVO, * 24.2-EVO versions from 24.2R2-EVO before 24.2R2-S1-EVO, * 24.4-EVO versions before 24.4R1-S3-EVO, 24.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 vulnerability in Juniper Networks Junos OS and Junos OS Evolved's routing protocol daemon (rpd) allows an unauthenticated, network-based attacker to cause denial of service by sending a specific BGP EVPN update message over an established BGP session, which triggers an rpd crash and restart. The issue stems from an improper check for unusual or exceptional conditions in how the rpd processes BGP EVPN updates.

MitigationApply the vendor-provided patches for the affected Junos OS/Evolved versions. Until patches can be applied, consider filtering or limiting BGP EVPN updates from untrusted peers, or disable BGP peering with untrusted neighbors as a temporary workaround.

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:= 23.4= 24.2= 24.4
Junos Os EvolvedOperating system
Affected:= 23.4= 24.2= 24.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
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 the Junos OS version
    Run 'show version' or 'show version detail' on the device CLI
    Affected if The version listed is 23.4, 24.2, or 24.4 (or a subversion within these release trains)
  2. Confirm BGP is enabled
    Run 'show configuration protocols bgp' to view BGP configuration
    Affected if BGP is configured and enabled on the device
  3. Verify BGP EVPN address family is configured
    Run 'show configuration protocols bgp family evpn' or inspect BGP group configurations for 'family evpn' statements
    Affected if BGP EVPN address family is configured under any BGP group or neighbor
  4. Check for established BGP EVPN peers
    Run 'show bgp neighbor' or 'show bgp summary' and look for peers in state Established with EVPN address family
    Affected if There are established BGP peers with EVPN capability
  5. Identify active BGP sessions accepting EVPN updates
    Review the BGP neighbor output for 'Family: EVPN' in the peer capabilities
    Affected if Any BGP neighbor shows EVPN family capability and is in Established state

You are affected if your Junos device runs version 23.4, 24.2, or 24.4 and has BGP with EVPN configured and active peers, as the attacker exploits established BGP EVPN sessions to trigger the rpd crash.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-provided patches for the affected Junos OS/Evolved versions. Until patches can be applied, consider filtering or limiting BGP EVPN updates from untrusted peers, or disable BGP peering with untrusted neighbors as a temporary workaround.

Recommended fix High confidence

Upgrade to Junos OS 23.4R2-S5+/24.2R2-S1+/24.4R1-S3 or 24.4R2, or Junos OS Evolved 23.4R2-S5-EVO+/24.2R2-S1-EVO+/24.4R1-S3-EVO or 24.4R2-EVO

  1. 1. Identify the current Junos OS or Junos OS Evolved version running on the device using 'show version'
  2. 2. Determine the upgrade path based on current version branch (23.4, 24.2, or 24.4)
  3. 3. For Junos OS 23.4: Upgrade to 23.4R2-S5 or later
  4. 4. For Junos OS 24.2: Upgrade to 24.2R2-S1 or later
  5. 5. For Junos OS 24.4: Upgrade to 24.4R1-S3 or 24.4R2 or later
  6. 6. For Junos OS Evolved 23.4: Upgrade to 23.4R2-S5-EVO or later
  7. 7. For Junos OS Evolved 24.2: Upgrade to 24.2R2-S1-EVO or later
  8. 8. For Junos OS Evolved 24.4: Upgrade to 24.4R1-S3-EVO or 24.4R2-EVO or later
Caveat Standard Junos upgrade may cause brief routing disruption as rpd restarts; ensure compatibility with existing configurations and review release notes for any known issues in target version

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
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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