dbcve.org
JunosOperating system · Juniper

CVE-2024-39516

HIGH · 7.5 CVSS v3.1 Published 2024-10-09
Fix available
A fix is available. Upgrade to 21.4 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 Out-of-Bounds Read vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated network-based attacker sending a specifically malformed 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 configured in either of two ways: * systems with BGP traceoptions enabled * systems with BGP traffic engineering configured This issue can affect iBGP and eBGP with any address family configured. The specific attribute involved is non-transitive, and will not propagate across a network. This issue affects: Junos OS:  * All versions before 21.4R3-S8, * 22.2 before 22.2R3-S5,  * 22.3 before 22.3R3-S4,  * 22.4 before 22.4R3-S3,  * 23.2 before 23.2R2-S2,  * 23.4 before 23.4R2;  Junos OS Evolved:  * All versions before 21.4R3-S8-EVO,  * 22.2-EVO before 22.2R3-S5-EVO,  * 22.3-EVO before 22.3R3-S4-EVO,  * 22.4-EVO before 22.4R3-S3-EVO,  * 23.2-EVO before 23.2R2-S2-EVO,  * 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

An out-of-bounds read vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated network-based attacker to send a specifically malformed BGP packet that causes rpd to crash and restart, creating a sustained DoS condition. The issue only affects systems with BGP traceoptions enabled or BGP traffic engineering configured.

MitigationApply the vendor-supplied Junos OS or Junos OS Evolved patches to the fixed versions (21.4R3-S8, 22.2R3-S5, 22.3R3-S4, 22.4R3-S3, 23.2R2-S2, 23.4R2 or later) after identifying affected systems with BGP traceoptions or traffic engineering enabled.

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.2= 22.3= 22.4= 23.2= 23.4
Junos Os EvolvedOperating system
Affected:< 21.4= 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 installed Junos OS version
    Run `show version` on the device CLI to obtain the exact Junos version installed
    Affected if Version matches one of the affected ranges: < 21.4, 21.4, 22.2, 22.3, 22.4, 23.2, or 23.4 (note: 23.4R1 is affected, 23.4R2 and later are fixed)
  2. Verify BGP is configured
    Run `show configuration protocols bgp | display set` to see if BGP protocol is configured on the device
    Affected if BGP is not configured at all - the device is not affected since the vulnerability requires an active BGP configuration
  3. Check if BGP traceoptions is enabled
    Run `show configuration protocols bgp traceoptions` or `show configuration protocols bgp | display set` and look for any traceoptions block under the BGP protocol configuration
    Affected if BGP traceoptions is enabled - this is one of the two conditions required for the vulnerability to be exploitable
  4. Check if BGP traffic engineering is configured
    Run `show configuration protocols bgp` and search for traffic-engineering related statements (such as traffic-engineering export or import policies)
    Affected if BGP traffic engineering is configured - this is the second condition required for the vulnerability to be exploitable

A device is affected if it runs a vulnerable Junos version AND has BGP configured with either traceoptions enabled or traffic engineering configured - both conditions must be present for the vulnerability to be exploitable.

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 Junos OS or Junos OS Evolved patches to the fixed versions (21.4R3-S8, 22.2R3-S5, 22.3R3-S4, 22.4R3-S3, 23.2R2-S2, 23.4R2 or later) after identifying affected systems with BGP traceoptions or traffic engineering enabled.

Recommended fix High confidence

Upgrade to the appropriate fixed release for your current branch: 21.4R3-S8/21.4R3-S8-EVO, 22.2R3-S5/22.2R3-S5-EVO, 22.3R3-S4/22.3R3-S4-EVO, 22.4R3-S3/22.4R3-S3-EVO, 23.2R2-S2/23.2R2-S2-EVO, or 23.4R2/23.4R2-EVO

  1. 1. Identify the current Junos OS or Junos OS Evolved version using 'show version' command
  2. 2. Confirm if the system has BGP traceoptions enabled (check configuration for 'protocols bgp traceoptions' under hierarchy) or BGP traffic engineering configured
  3. 3. For Junos OS: Upgrade to 21.4R3-S8 or later, or 22.2R3-S5 or later, or 22.3R3-S4 or later, or 22.4R3-S3 or later, or 23.2R2-S2 or later, or 23.4R2 or later
  4. 4. For Junos OS Evolved: Upgrade to 21.4R3-S8-EVO or later, or 22.2R3-S5-EVO or later, or 22.3R3-S4-EVO or later, or 22.4R3-S3-EVO or later, or 23.2R2-S2-EVO or later, or 23.4R2-EVO or later
  5. 5. Schedule maintenance window as upgrade will require system reboot
  6. 6. Backup current configuration before performing upgrade
  7. 7. After upgrade, verify rpd process is running with 'show system processes routing'
Caveat Point releases typically maintain configuration compatibility; however, always review Juniper release notes for any behavior changes before upgrading

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 / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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