CVE-2025-21598

Junos OS and Junos OS Evolved: When BGP traceoptions are configured, receipt of malformed BGP packets causes RPD to crash

HIGH
7.5
CVSS Score
Published: January 9, 2025 at 06:16 PM UTC
Updated: June 17, 2026 at 08:43 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.7%
SSVC
No known exploit

Description

An Out-of-bounds Read vulnerability in Juniper Networks Junos OS and Junos OS Evolved's routing protocol daemon (rpd) allows an unauthenticated, network-based attacker to send malformed BGP packets to a device configured with packet receive trace options enabled to crash rpd. This issue affects: Junos OS: * from 21.2R3-S8 before 21.2R3-S9,  * from 21.4R3-S7 before 21.4R3-S9,  * from 22.2R3-S4 before 22.2R3-S5,  * from 22.3R3-S2 before 22.3R3-S4,  * from 22.4R3 before 22.4R3-S5,  * from 23.2R2 before 23.2R2-S2,  * from 23.4R1 before 23.4R2-S1,  * from 24.2R1 before 24.2R1-S1, 24.2R2. Junos OS Evolved: * from 21.4R3-S7-EVO before 21.4R3-S9-EVO,  * from 22.2R3-S4-EVO before 22.2R3-S5-EVO,  * from 22.3R3-S2-EVO before 22.3R3-S4-EVO,  * from 22.4R3-EVO before 22.4R3-S5-EVO,  * from 23.2R2-EVO before 23.2R2-S2-EVO,  * from 23.4R1-EVO before 23.4R2-S1-EVO,  * from 24.2R1-EVO before 24.2R1-S2-EVO, 24.2R2-EVO. This issue requires a BGP session to be established. This issue can propagate and multiply through multiple ASes until reaching vulnerable devices. This issue affects iBGP and eBGP. This issue affects IPv4 and IPv6. An indicator of compromise may be the presence of malformed update messages in a neighboring AS which is unaffected by this issue: For example, by issuing the command on the neighboring device:  show log messages Reviewing for similar messages from devices within proximity to each other may indicate this malformed packet is propagating:   rpd[<pid>]: Received malformed update from <IP address> (External AS <AS#>) and   rpd[<pid>]: Malformed Attribute

Affected

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

21.2R3-S8 ≤ v < 21.2R3-S921.4R3-S7 ≤ v < 21.4R3-S922.2R3-S4 ≤ v < 22.2R3-S522.3R3-S2 ≤ v < 22.3R3-S422.4R3 ≤ v < 22.4R3-S523.2R2 ≤ v < 23.2R2-S223.4R1 ≤ v < 23.4R2-S124.2R1 ≤ v < 24.2R1-S1, 24.2R221.2 r3-s821.2R3-S821.4 r3-s721.4 r3-s821.4R3-S722.2 r3-s422.2R3-S422.3 r3-s222.3 r3-s322.3R3-S222.4 r322.4 r3-s122.4 r3-s222.4 r3-s322.4 r3-s422.4R323.2 r223.2 r2-s123.2R223.4 r123.4 r1-s123.4 r1-s223.4 r223.4R124.2 r124.2 r224.2R1
Affected range stops below 21.2R3-S9, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.4R3-S9, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.2R3-S5, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.3R3-S4, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.4R3-S5, 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 23.4R2-S1, so it looks safe — our inference, not a vendor statement
Affected range stops below 24.2R1-S1, 24.2R2, so it looks safe — our inference, not a vendor statement
21.4R3-S7-EVO ≤ v < 21.4R3-S9-EVO22.2R3-S4-EVO ≤ v < 22.2R3-S5-EVO22.3R3-S2-EVO ≤ v < 22.3R3-S4-EVO22.4R3-EVO ≤ v < 22.4R3-S5-EVO23.2R2-EVO ≤ v < 23.2R2-S2-EVO23.4R1-EVO ≤ v < 23.4R2-S1-EVO24.2R1-EVO ≤ v < 24.2R1-S2-EVO, 24.2R2-EVO21.4R3-S7-EVO22.2R3-S4-EVO22.3R3-S2-EVO22.4R3-EVO23.2R2-EVO23.4R1-EVO24.2R1-EVO
Affected range stops below 21.4R3-S9-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.2R3-S5-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.3R3-S4-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.4R3-S5-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 23.2R2-S2-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 23.4R2-S1-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 24.2R1-S2-EVO, 24.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-125

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