CVE-2024-39547

Junos OS and Junos OS Evolved: cRPD: Receipt of crafted TCP traffic can trigger high CPU utilization

HIGH
7.5
CVSS Score
Published: October 11, 2024 at 03:20 PM UTC
Updated: June 17, 2026 at 07:42 AM UTC
4 products affected across 2 vendorsJunos Containerized Routing Protocol DaemonJunosJunos OS Evolved

Using Junos OS by Juniper Networks?

Get instant alerts when new vulnerabilities affect Junos OS - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 1.0%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

All versions
juniper-junos-os-evolved (environment) · juniper-networks-junos (environment)
v < 21.4r3-s7-evo22.2-evo ≤ v < 22.2r3-s4-evo22.3-evo ≤ v < 22.3r3-s3-evo22.4-evo ≤ v < 22.4r3-s2-evo23.2-evo ≤ v < 23.2r2-evo22.2-evo22.3-evo22.4-evo23.2-evo
Affected range stops below 21.4r3-s7-evo, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.2r3-s4-evo, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.3r3-s3-evo, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.4r3-s2-evo, so it looks safe — our inference, not a vendor statement
Affected range stops below 23.2r2-evo, so it looks safe — our inference, not a vendor statement
v < 21.2R3-S8v < 21.2r3-s821.4 ≤ v < 21.4R3-S721.4 ≤ v < 21.4r3-s722.1 ≤ v < 22.1R3-S622.1 ≤ v < 22.1r3-s622.2 ≤ v < 22.2R3-S422.2 ≤ v < 22.2r3-s422.3 ≤ v < 22.3R3-S322.3 ≤ v < 22.3r3-s322.4 ≤ v < 22.4R3-S222.4 ≤ v < 22.4r3-s223.2 ≤ v < 23.2R2-S223.2 ≤ v < 23.2r2-s224.2 ≤ v < 24.2R224.2 ≤ v < 24.2r221.422.122.222.322.423.224.2
Affected range stops below 21.2R3-S8, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.4R3-S7, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.1R3-S6, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.2R3-S4, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.3R3-S3, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.4R3-S2, so it looks safe — our inference, not a vendor statement
Affected range stops below 23.2R2-S2, so it looks safe — our inference, not a vendor statement
Affected range stops below 24.2R2, so it looks safe — our inference, not a vendor statement
v < 21.4R3-S7-EVO22.2-EVO ≤ v < 22.2R3-S4-EVO22.3-EVO ≤ v < 22.3R3-S3-EVO22.4-EVO ≤ v < 22.4R3-S2-EVO23.2-EVO ≤ v < 23.2R2-EVO22.2-EVO22.3-EVO22.4-EVO23.2-EVO
Affected range stops below 21.4R3-S7-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.2R3-S4-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.3R3-S3-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.4R3-S2-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 23.2R2-EVO, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHjuniper
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-755

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card