dbcve.org
JunosOperating system · Juniper

CVE-2024-39552

HIGH · 7.5 CVSS v3.1 Published 2024-07-11
Fix available
A fix is available. Upgrade to 20.4 / 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 a network based, unauthenticated attacker to cause the RPD process to crash leading to a Denial of Service (DoS). When a malformed BGP UPDATE packet is received over an established BGP session, RPD crashes and restarts. Continuous receipt of the malformed BGP UPDATE messages will create a sustained Denial of Service (DoS) condition for impacted devices. This issue affects eBGP and iBGP, in both IPv4 and IPv6 implementations. This issue requires a remote attacker to have at least one established BGP session. This issue affects: Juniper Networks Junos OS: * All versions earlier than 20.4R3-S9; * 21.2 versions earlier than 21.2R3-S7; * 21.3 versions earlier than 21.3R3-S5; * 21.4 versions earlier than 21.4R3-S6; * 22.1 versions earlier than 22.1R3-S4; * 22.2 versions earlier than 22.2R3-S3; * 22.3 versions earlier than 22.3R3-S2; * 22.4 versions earlier than 22.4R3; * 23.2 versions earlier than 23.2R2. Juniper Networks Junos OS Evolved: * All versions earlier than 21.2R3-S7; * 21.3-EVO versions earlier than 21.3R3-S5; * 21.4-EVO versions earlier than 21.4R3-S8; * 22.1-EVO versions earlier than 22.1R3-S4; * 22.2-EVO versions earlier than 22.2R3-S3; * 22.3-EVO versions earlier than 22.3R3-S2; * 22.4-EVO versions earlier than 22.4R3; * 23.2-EVO versions earlier than 23.2R2.

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 the routing protocol daemon (RPD) of Juniper Junos OS and Junos OS Evolved allows a remote, unauthenticated attacker with an established BGP session to send malformed BGP UPDATE packets that cause RPD to crash and restart, creating a sustained DoS condition.

MitigationApply the vendor-supplied software updates (upgrade to the fixed versions listed in the advisory) to affected devices.

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:< 20.4= 20.4= 21.2= 21.3= 21.4= 22.1= 22.2= 22.3= 22.4= 23.2
Junos Os EvolvedOperating system
Affected:< 21.2= 21.2= 21.3= 21.4= 22.1= 22.2= 22.3= 22.4= 23.2

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 installed
    Execute 'show version' or 'show version detail' on the device CLI to retrieve the installed software version
    Affected if The version shown matches any of these: for Junos (all variants) versions < 20.4, = 20.4, = 21.2, = 21.3, = 21.4, = 22.1, = 22.2, = 22.3, = 22.4, = 23.2; for Junos OS Evolved versions < 21.2, = 21.2, = 21.3, = 21.4, = 22.1, = 22.2, = 22.3, = 22.4, = 23.2
  2. Verify BGP protocol is configured
    Execute 'show configuration protocols bgp' or 'show bgp summary' to determine if BGP is actively configured on the device
    Affected if BGP is configured and operational (the vulnerability requires an established BGP session to be exploited)
  3. Confirm RPD process status
    Execute 'show system processes routing' or check 'sysctl -a | grep rpd' to verify the routing daemon is running
    Affected if RPD is running and handling BGP sessions - the crash only occurs when malformed BGP UPDATE packets are received by the active routing daemon

You are affected if your Junos device runs any version listed as vulnerable AND has BGP protocol configured and operational.

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 20.4 / 21.2 or later
Fixed in 20.421.2
Interim mitigation

Apply the vendor-supplied software updates (upgrade to the fixed versions listed in the advisory) to affected devices.

Recommended fix High confidence

Junos OS: upgrade to 20.4R3-S9 / 21.2R3-S7 / 21.3R3-S5 / 21.4R3-S6 / 22.1R3-S4 / 22.2R3-S3 / 22.3R3-S2 / 22.4R3 / 23.2R2; Junos OS Evolved: upgrade to 21.2R3-S7 / 21.3R3-S5 / 21.4R3-S8 / 22.1R3-S4 / 22.2R3-S3 / 22.3R3-S2 / 22.4R3 / 23.2R2

  1. 1. Identify the current Junos OS or Junos OS Evolved version running on the device using 'show version'
  2. 2. Determine the appropriate upgrade path based on the current version branch (20.4, 21.2, 21.3, 21.4, 22.1, 22.2, 22.3, 22.4, or 23.2)
  3. 3. For Junos OS: upgrade to 20.4R3-S9, 21.2R3-S7, 21.3R3-S5, 21.4R3-S6, 22.1R3-S4, 22.2R3-S3, 22.3R3-S2, 22.4R3, or 23.2R2 (whichever is the next available release in your version branch)
  4. 4. For Junos OS Evolved: upgrade to 21.2R3-S7, 21.3R3-S5, 21.4R3-S8, 22.1R3-S4, 22.2R3-S3, 22.3R3-S2, 22.4R3, or 23.2R2 (whichever is the next available release in your version branch)
  5. 5. Download the appropriate upgrade package from the Juniper Networks support portal
  6. 6. Upload the software package to the device using 'file copy' or USB
  7. 7. Initiate the upgrade using 'request system software add <package>'
  8. 8. After upgrade completes, verify the new version with 'show version'
Caveat Standard Junos upgrade considerations apply - review release notes for your version branch for any configuration changes or compatibility notices

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

Fix this in Junos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
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,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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