dbcve.org
JunosOperating system · Juniper

CVE-2024-39525

HIGH · 7.5 CVSS v3.1 Published 2024-10-09
Fix available
A fix is available. Upgrade to 21.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 Improper Handling of Exceptional Conditions vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated network-based attacker sending a specific BGP packet to cause rpd to crash and restart, resulting in a Denial of Service (DoS). Continued receipt and processing of this packet will create a sustained Denial of Service (DoS) condition. This issue only affects systems with BGP traceoptions enabled and requires a BGP session to be already established.  Systems without BGP traceoptions enabled are not affected by this issue. This issue affects iBGP and eBGP, and both IPv4 and IPv6 are affected by this vulnerability. This issue affects: Junos OS:  * All versions before 21.2R3-S8,  * from 21.4 before 21.4R3-S8,  * from 22.2 before 22.2R3-S4,  * from 22.3 before 22.3R3-S4, * from 22.4 before 22.4R3-S3,  * from 23.2 before 23.2R2-S1,  * from 23.4 before 23.4R2;  Junos OS Evolved:  * All versions before 21.2R3-S8-EVO,  * from 21.4-EVO before 21.4R3-S8-EVO,  * from 22.2-EVO before 22.2R3-S4-EVO,  * from 22.3-EVO before 22.3R3-S4-EVO, * from 22.4-EVO before 22.4R3-S3-EVO,  * from 23.2-EVO before 23.2R2-S1-EVO,  * from 23.4-EVO 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 denial of service vulnerability exists in Juniper's routing protocol daemon (rpd) where an unauthenticated network attacker with an established BGP session can send specific BGP packets to cause rpd to crash and restart. The vulnerability is only exploitable when BGP traceoptions are enabled, and continued receipt of the malicious packet creates a sustained DoS condition.

MitigationDisable BGP traceoptions if not required for troubleshooting, or apply the vendor-supplied patches for your Junos OS/Evolved version. Until patched, monitor for rpd crashes and implement BGP session monitoring to detect exploitation attempts.

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.2= 21.2= 21.4= 22.2= 22.3= 22.4= 23.2= 23.4
Junos Os EvolvedOperating system
Affected:< 21.2= 21.2= 21.4= 22.2= 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/Evolved version
    Run 'show version' or 'show version detail' to obtain the installed version. Compare it against the affected versions: < 21.2, = 21.2, = 21.4, = 22.2, = 22.3, = 22.4, = 23.2, = 23.4
    Affected if The installed version matches any of the affected versions listed in the CVE
  2. Verify BGP traceoptions configuration
    Run 'show configuration protocols bgp | display set' or inspect the configuration under 'protocols bgp group <name> traceoptions' to determine if BGP traceoptions are enabled
    Affected if BGP traceoptions are configured and enabled on any BGP group or neighbor
  3. Inspect for rpd crash logs
    Run 'show log messages' or 'show system crash' and search for recent rpd crash events, particularly those mentioning BGP-related causes
    Affected if Recent rpd crashes are present in the logs, especially correlated with BGP activity
  4. Check BGP session status
    Run 'show bgp summary' to verify BGP sessions are established and stable
    Affected if BGP sessions exist and the device is vulnerable if traceoptions are enabled on affected versions

The device is affected if it runs a Junos version matching the affected list AND has BGP traceoptions enabled, which would allow an attacker with an established BGP session to trigger rpd crashes.

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.2 or later
Fixed in 21.2
Interim mitigation

Disable BGP traceoptions if not required for troubleshooting, or apply the vendor-supplied patches for your Junos OS/Evolved version. Until patched, monitor for rpd crashes and implement BGP session monitoring to detect exploitation attempts.

Recommended fix High confidence

Upgrade to 21.2R3-S8 / 21.4R3-S8 / 22.2R3-S4 / 22.3R3-S4 / 22.4R3-S3 / 23.2R2-S1 / 23.4R2 or later (select based on your current branch)

  1. 1. Identify the current Junos OS or Junos OS Evolved version using 'show version' command
  2. 2. Determine if BGP traceoptions are enabled using 'show configuration protocols bgp | display set | match traceoptions'
  3. 3. If BGP traceoptions are enabled, consider disabling them as a temporary mitigation using 'delete protocols bgp traceoptions' in configuration mode and commit the change
  4. 4. Plan an upgrade to a fixed version based on your current branch: For 21.2.x branch upgrade to 21.2R3-S8 or later; For 21.4.x branch upgrade to 21.4R3-S8 or later; For 22.2.x branch upgrade to 22.2R3-S4 or later; For 22.3.x branch upgrade to 22.3R3-S4 or later; For 22.4.x branch upgrade to 22.4R3-S3 or later; For 23.2.x branch upgrade to 23.2R2-S1 or later; For 23.4.x branch upgrade to 23.4R2 or
  5. 5. Before upgrading, backup the current configuration using 'request system configuration rescue save'
  6. 6. Perform the upgrade following standard Junos upgrade procedures - typically using 'request system software add <package>' with appropriate options for your hardware platform
  7. 7. After upgrade, verify the new version is running using 'show version' and confirm BGP peering is established using 'show bgp summary'
  8. 8. Re-enable BGP traceoptions after upgrade if needed, as the fixed versions address the vulnerability
Caveat Review Juniper release notes for your target version for any potential compatibility issues or configuration changes; ensure adequate maintenance window for upgrade and testing

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

Fix this in Junos Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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