dbcve.org
Junos Containerized Routing Protocol DaemonApplication · Juniper

CVE-2024-39547

HIGH · 7.5 CVSS v3.1 Published 2024-10-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
An Improper Handling of Exceptional Conditions vulnerability in the rpd-server of Juniper Networks Junos OS and Junos OS Evolved within cRPD allows an unauthenticated network-based attacker sending crafted TCP traffic to the routing engine (RE) to cause a CPU-based Denial of Service (DoS). If specially crafted TCP traffic is received by the control plane, or a TCP session terminates unexpectedly, it will cause increased control plane CPU utilization by the rpd-server process. While not explicitly required, the impact is more severe when RIB sharding is enabled. Task accounting shows unexpected reads by the RPD Server jobs for shards: user@junos> show task accounting detail ... read:RPD Server.0.0.0.0+780.192.168.0.78+48886 TOT:00000003.00379787 MAX:00000000.00080516 RUNS: 233888\ read:RPD Server.0.0.0.0+780.192.168.0.78+49144 TOT:00000004.00007565 MAX:00000000.00080360 RUNS: 233888\ read:RPD Server.0.0.0.0+780.192.168.0.78+49694 TOT:00000003.00600584 MAX:00000000.00080463 RUNS: 233888\ read:RPD Server.0.0.0.0+780.192.168.0.78+50246 TOT:00000004.00346998 MAX:00000000.00080338 RUNS: 233888\ This issue affects: Junos OS with cRPD:  * All versions before 21.2R3-S8,  * 21.4 before 21.4R3-S7,  * 22.1 before 22.1R3-S6,  * 22.2 before 22.2R3-S4,  * 22.3 before 22.3R3-S3,  * 22.4 before 22.4R3-S2,  * 23.2 before 23.2R2-S2,  * 24.2 before 24.2R2;  Junos OS Evolved with cRPD:  * All versions before 21.4R3-S7-EVO,  * 22.2 before 22.2R3-S4-EVO,  * 22.3 before 22.3R3-S3-EVO,  * 22.4 before 22.4R3-S2-EVO,  * 23.2 before 23.2R2-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 improper handling of exceptional conditions vulnerability in the rpd-server (routing protocol daemon) of Juniper Networks Junos OS and Junos OS Evolved with cRPD allows an unauthenticated network-based attacker to send crafted TCP traffic to the routing engine, causing increased control plane CPU utilization and a denial-of-service condition. The issue is exacerbated when RIB sharding is enabled.

MitigationApply the vendor-supplied patches: upgrade to Junos OS versions 21.2R3-S8, 21.4R3-S7, 22.1R3-S6, 22.2R3-S4, 22.3R3-S3, 22.4R3-S2, 23.2R2-S2, or 24.2R2 or later (or equivalent EVO versions) per the advisory. Consider disabling RIB sharding as a temporary mitigation if unable to patch immediately.

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
Junos Containerized Routing Protocol DaemonApplication
Affected:all versions

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. Verify cRPD is running
    Check if the Junos Containerized Routing Protocol Daemon (cRPD) container or process is active on the system. Use commands such as 'docker ps' or 'podman ps' to list running containers, or check for rpd processes with 'ps aux | grep rpd'.
    Affected if cRPD container or rpd process is running on the system
  2. Confirm RIB sharding configuration
    Inspect the cRPD configuration for RIB sharding settings. Check configuration files or run 'cRPD CLI commands' to display the RIB sharding status. Look for 'sharding' or 'shard' configuration statements under the routing options.
    Affected if RIB sharding is explicitly enabled in the cRPD configuration (this worsens the DoS impact)
  3. Identify cRPD version
    Retrieve the installed cRPD version. Use 'docker images' or 'podman images' to list the cRPD container image with its tag, or run 'cRPD command' to display the version from within the container.
    Affected if Any version of cRPD is installed (the advisory states all versions are affected)
  4. Assess network exposure of routing engine
    Review firewall rules, access control lists, or network segmentation around the routing engine. Determine if TCP traffic to the routing engine (port 179 for BGP or other routing ports) is reachable from untrusted network segments.
    Affected if The routing engine is accessible from untrusted network sources, allowing an unauthenticated attacker to send crafted TCP traffic

If cRPD is running and its routing engine interface is reachable from untrusted networks, the system is vulnerable to this DoS flaw regardless of version, especially if RIB sharding is enabled.

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

Apply the vendor-supplied patches: upgrade to Junos OS versions 21.2R3-S8, 21.4R3-S7, 22.1R3-S6, 22.2R3-S4, 22.3R3-S3, 22.4R3-S2, 23.2R2-S2, or 24.2R2 or later (or equivalent EVO versions) per the advisory. Consider disabling RIB sharding as a temporary mitigation if unable to patch immediately.

Recommended fix High confidence

Upgrade to 24.2R2 (or latest stable) for Junos OS with cRPD, or 23.2R2-EVO for Junos OS Evolved with cRPD

  1. 1. Identify the current cRPD version by running 'show version' on the device
  2. 2. Determine the product family (Junos OS with cRPD or Junos OS Evolved with cRPD)
  3. 3. For Junos OS with cRPD: Upgrade to one of the fixed versions: 21.2R3-S8, 21.4R3-S7, 22.1R3-S6, 22.2R3-S4, 22.3R3-S3, 22.4R3-S2, 23.2R2-S2, or 24.2R2
  4. 4. For Junos OS Evolved with cRPD: Upgrade to one of the fixed versions: 21.4R3-S7-EVO, 22.2R3-S4-EVO, 22.3R3-S3-EVO, 22.4R3-S2-EVO, or 23.2R2-EVO
  5. 5. Download the appropriate upgrade package from the Juniper Networks support portal
  6. 6. Install the upgrade following standard Junos upgrade procedures
  7. 7. After upgrade, verify the rpd-server process is running normally with 'show system processes extensive | match rpd'
  8. 8. Confirm the fix by checking 'show task accounting detail' to ensure no unexpected reads from RPD Server jobs
Caveat Standard Junos upgrade precautions apply - ensure compatibility with existing configurations and test in lab environment before production deployment

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

Fix this in Junos Containerized Routing Protocol Daemon 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 help mitigating

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-39547 — 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-39547 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