CVE 5.3 MEDIUM

Junos OS and Junos OS Evolved: With BGP sharding enabled, change in indirect next-hop can cause RPD crash_CVE-2025-59962

5.3 / 10
MEDIUM
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Description

An Access of Uninitialized Pointer vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved with BGP sharding configured allows an attacker triggering indirect next-hop updates, along with timing outside the attacker's control, to cause rpd to crash and restart, leading to a Denial of Service (DoS).

With BGP sharding enabled, triggering route resolution of an indirect next-hop (e.g., an IGP route change over which a BGP route gets resolved), may cause rpd to crash and restart. An attacker causing continuous IGP route churn, resulting in repeated route re-resolution, will increase the likelihood of triggering this issue, leading to a potentially extended DoS condition.

This issue affects:

Junos OS:



* all versions before 21.4R3-S6, 
* from 22.1 before 22.1R3-S6, 
* from 22.2 before 22.2R3-S3, 
* from 22.3 before 22.3R3-S3, 
* from 22.4 before 22.4R3, 
* from 23.2 before 23.2R2; 




Junos OS Evolved: 



* all versions before 22.3R3-S3-EVO, 
* from 22.4 before 22.4R3-EVO, 
* from 23.2 before 23.2R2-EVO.




Versions before Junos OS 21.3R1 and Junos OS Evolved 21.3R1-EVO are unaffected by this issue.

Basic Information

ID CVE-2025-59962
Source juniper
Published Oct 9, 2025 at 15:45
Modified Oct 9, 2025 at 19:05

Affected Product

Vendor Juniper Networks
Product Junos OS
Version 21.4
Affected Versions Juniper Networks Junos OS 21.4
Juniper Networks Junos OS 22.1
Juniper Networks Junos OS 22.2
Juniper Networks Junos OS 22.3
Juniper Networks Junos OS 22.4
Juniper Networks Junos OS 23.2
Juniper Networks Junos OS Evolved 22.3
Juniper Networks Junos OS Evolved 22.4
Juniper Networks Junos OS Evolved 23.2

CWE Classification

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.