CVE-2024-39552

Junos OS and Junos OS Evolved: Malformed BGP UPDATE causes RPD crash

HIGH
7.5
CVSS Score
Published: July 11, 2024 at 04:30 PM UTC
Updated: June 17, 2026 at 07:42 AM UTC
3 products affected across 2 vendorsJunosJunos OS EvolvedJunos 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 0.6%
SSVC
No known exploit

Description

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.

Affected

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

Affected range stops below 21.2r3-s7, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.3r3-s5, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.4r3-s8, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.1r3-s4, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.2r3-s3, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.3r3-s2, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.4r3, so it looks safe — our inference, not a vendor statement
Affected range stops below 23.2r2, so it looks safe — our inference, not a vendor statement
Affected range stops below 23.4r1, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.4R3-S9, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.2R3-S7, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.3R3-S6, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.4R3-S6, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.1R3-S4, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.2R3-S3, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.3R3-S2, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.4R3, so it looks safe — our inference, not a vendor statement
Affected range stops below 23.2R2, so it looks safe — our inference, not a vendor statement
v < 21.2R3-S7-EVO21.3-EVO ≤ v < 21.3R3-S5-EVO21.4-EVO ≤ v < 21.4R3-S8-EVO22.1-EVO ≤ v < 22.1R3-S4-EVO22.2-EVO ≤ v < 22.2R3-S3-EVO22.3-EVO ≤ v < 22.3R3-S2-EVO22.4-EVO ≤ v < 22.4R3-EVO23.2-EVO ≤ v < 23.2R2-EVO23.4-EVO ≤ v < 23.4R1-EVO21.3-EVO21.4-EVO22.1-EVO22.2-EVO22.3-EVO22.4-EVO23.2-EVO23.4-EVO
Affected range stops below 21.2R3-S7-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.3R3-S5-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.4R3-S8-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.1R3-S4-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.2R3-S3-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.3R3-S2-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.4R3-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
Affected range stops below 23.4R1-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