dbcve.org
JunosOperating system · Juniper

CVE-2025-52980

HIGH · 7.5 CVSS v3.1 Published 2025-07-11
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
A Use of Incorrect Byte Ordering vulnerability in the Routing Protocol Daemon (rpd) of Juniper Networks Junos OS on SRX300 Series allows an unauthenticated, network-based attacker to cause a Denial-of-Service (DoS). When a BGP update is received over an established BGP session which contains a specific, valid, optional, transitive path attribute, rpd will crash and restart. This issue affects eBGP and iBGP over IPv4 and IPv6. This issue affects: Junos OS: * 22.1 versions from 22.1R1 before 22.2R3-S4, * 22.3 versions before 22.3R3-S3, * 22.4 versions before 22.4R3-S2, * 23.2 versions before 23.2R2, * 23.4 versions before 23.4R2.

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 byte-ordering vulnerability exists in Junos OS rpd when processing BGP updates containing specific optional transitive path attributes. The incorrect byte ordering during attribute parsing causes rpd to crash and restart, resulting in denial of service.

MitigationUpgrade Junos OS to a patched version (22.2R3-S4, 22.3R3-S3, 22.4R3-S2, 23.2R2, 23.4R2 or later). For external BGP peers, implement strict peering controls and consider filtering at network edges, though this may not fully mitigate as the attribute is valid.

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:= 22.1= 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
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. Check Junos OS version
    Run 'show version' or 'show version detail' to retrieve the installed Junos OS version
    Affected if The version matches 22.1, 22.3, 22.4, 23.2, or 23.4 exactly
  2. Confirm BGP is enabled
    Run 'show bgp summary' or check configuration with 'show configuration protocols bgp'
    Affected if BGP protocol is configured and enabled on the device
  3. Check for active BGP peers
    Run 'show bgp neighbor' to list established BGP peers
    Affected if The device has external or internal BGP peers established
  4. Verify rpd process status
    Run 'show system processes routing' to confirm rpd is running
    Affected if rpd is active and processing BGP updates

The device is affected if it runs Junos OS version 22.1, 22.3, 22.4, 23.2, or 23.4 and has BGP configured with active peers receiving updates.

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

Upgrade Junos OS to a patched version (22.2R3-S4, 22.3R3-S3, 22.4R3-S2, 23.2R2, 23.4R2 or later). For external BGP peers, implement strict peering controls and consider filtering at network edges, though this may not fully mitigate as the attribute is valid.

Recommended fix High confidence

22.2R3-S4 (for 22.1 branch); 22.3R3-S3 (for 22.3 branch); 22.4R3-S2 (for 22.4 branch); 23.2R2 (for 23.2 branch); 23.4R2 (for 23.4 branch)

  1. 1. Identify the current Junos OS version on the SRX300 device using 'show version'
  2. 2. Determine which version branch (22.1, 22.3, 22.4, 23.2, or 23.4) the current device is running
  3. 3. For 22.1 branch: upgrade to 22.2R3-S4 or later
  4. 4. For 22.3 branch: upgrade to 22.3R3-S3 or later
  5. 5. For 22.4 branch: upgrade to 22.4R3-S2 or later
  6. 6. For 23.2 branch: upgrade to 23.2R2 or later
  7. 7. For 23.4 branch: upgrade to 23.4R2 or later
  8. 8. Upload the upgrade package to the device via SCP or USB
Caveat Standard Junos upgrade considerations apply - review release notes for any configuration changes, ensure backups exist before upgrade

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

Fix this in Junos Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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