dbcve.org
JunosOperating system · Juniper

CVE-2024-39564

HIGH · 7.5 CVSS v3.1 Published 2025-02-05
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
This is a similar, but different vulnerability than the issue reported as CVE-2024-39549. A double-free vulnerability in the routing process daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an attacker to send a malformed BGP Path attribute update which allocates memory used to log the bad path attribute. This double free of memory is causing an rpd crash, leading to a Denial of Service (DoS). This issue affects: Junos OS:  * from 22.4 before 22.4R3-S4. Junos OS Evolved: * from 22.4 before 22.4R3-S4-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 double-free vulnerability in the routing process daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an attacker to send a malformed BGP Path attribute update. This triggers a double free of memory that was allocated to log the bad path attribute, causing the rpd process to crash and resulting in a Denial of Service.

MitigationApply vendor patches (Junos OS 22.4R3-S4 or later / Junos OS Evolved 22.4R3-S4-EVO or later). As an interim measure, implement BGP peering filters to reject malformed path attributes at edge routers.

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. Identify Junos OS version
    Run 'show version' or 'show version detail' on the device CLI to obtain the installed software version.
    Affected if The displayed version matches any of the affected versions: 21.2, 21.4, 22.2, 22.3, 22.4, 23.2, 23.4, or any version prior to 21.2.
  2. Confirm product type
    Run 'show version' and check if the output indicates 'Junos OS Evolved' versus standard 'Junos OS'. Both product lines are affected.
    Affected if The device runs either Junos OS or Junos OS Evolved and the version matches the affected list.
  3. Verify BGP protocol is configured
    Run 'show configuration protocols bgp' or 'show bgp summary' to determine if BGP peering is enabled on the device.
    Affected if BGP is actively configured, as the vulnerability is triggered by malformed BGP path attribute updates.
  4. Confirm rpd process is running
    Run 'show system processes routing' or 'show system processes' to verify the routing daemon (rpd) is active.
    Affected if The rpd process is running, as this is the component that crashes when exploited.

The environment is affected if the device runs a vulnerable Junos OS or Junos OS Evolved version (21.2, 21.4, 22.2-22.4, 23.2, 23.4, or <21.2) with BGP protocol configured and the rpd process active.

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

Apply vendor patches (Junos OS 22.4R3-S4 or later / Junos OS Evolved 22.4R3-S4-EVO or later). As an interim measure, implement BGP peering filters to reject malformed path attributes at edge routers.

Recommended fix High confidence

Junos OS: 22.4R3-S4 or later; Junos OS Evolved: 22.4R3-S4-EVO or later

  1. 1. Identify the current Junos OS or Junos OS Evolved version running on the affected device using 'show version' command.
  2. 2. If the device is running a version from 22.4 before 22.4R3-S4 (for Junos OS) or 22.4 before 22.4R3-S4-EVO (for Junos OS Evolved), plan for an upgrade.
  3. 3. Schedule a maintenance window as the upgrade will require a system reboot.
  4. 4. Download the fixed release (22.4R3-S4 or later for Junos OS; 22.4R3-S4-EVO or later for Junos OS Evolved) from the Juniper support portal.
  5. 5. Upload the Junos upgrade package to the device using 'file copy' or similar method.
  6. 6. Install the upgrade using 'request system software add <package>' command.
  7. 7. Reboot the device using 'request system reboot' command to complete the installation.
  8. 8. After reboot, verify the new version is running using 'show version' and confirm the fix is applied.
Caveat Upgrade requires a system reboot and should be performed during a maintenance window. Always review release notes for any migration or compatibility considerations before upgrading.

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

Fix this in Junos Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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