Product Affected

This issue affects all versions of Junos OS and Junos OS Evolved.
Medium

Problem

A NULL Pointer Dereference vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, network-based attacker to cause impact to the availability of the device.

When static route points to a reject next hop and a gNMI query is processed for that static route, rpd crashes and restarts.

This issue affects:

Junos OS: 

  • all versions before 21.2R3-S9,
  • 21.4 versions before 21.4R3-S10, 
  • 22.2 versions before 22.2R3-S6,
  • 22.4 versions before 22.4R3-S6,
  • 23.2 versions before 23.2R2-S3,
  • 23.4 versions before 23.4R2-S4,
  • 24.2 versions before 24.2R1-S2, 24.2R2;

 

Junos OS Evolved:

  • all versions before 22.4R3-S7-EVO,
  • 23.2-EVO versions before 23.2R2-S3-EVO,
  • 23.4-EVO versions before 23.4R2-S4-EVO,
  • 24.2-EVO versions before 24.2R2-EVO.

 

To be exposed to this issue the system needs to be configured for GRPC:

[ system services extension-service request-response grpc ]

and a static route needs to point to a reject next-hop as shown in the following example:

[ routing-options static route 192.0.2.0/24 next-hop 198.51.100.1 resolve ]
[ routing-options static route 198.51.100.1/32 reject]

 

Juniper SIRT is not aware of any malicious exploitation of this vulnerability.

 

This issue was found during internal product security testing or research.

Solution

The following software releases have been updated to resolve this specific issue:
Junos OS Evolved: 22.4R3-S7-EVO, 23.2R2-S3-EVO, 23.4R2-S4-EVO, 24.2R2-EVO, 24.4R1-EVO, and all subsequent releases;
Junos OS: 21.2R3-S9, 21.4R3-S10, 22.2R3-S6, 22.4R3-S6, 23.2R2-S3, 23.4R2-S4, 24.2R1-S2, 24.2R2, 24.4R1, and all subsequent releases.

 

This issue is being tracked as 1809740 which is visible on the Customer Support website.

 

Note: Juniper SIRT's policy is not to evaluate releases which are beyond End of Engineering (EOE) or End of Life (EOL).

Workaround

There are no known workarounds for this issue.


To reduce the risk of exploitation use access lists or firewall filters to limit access to the device only from trusted, administrative networks or hosts, and configure authentication for grpc.

Severity Assessment

Information for how Juniper Networks uses CVSS can be found at KB 16446 [juniper.net] "Common Vulnerability Scoring System (CVSS) and Juniper's Security Advisories."

Modification History

2025-07-09: Initial Publication

2025-07-10: Fixed the title to align the the rest of the JSA to say reject next-hop

Related Information