An Out-of-Bounds Read vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, logically adjacent BGP peer sending a specifically malformed BGP packet to cause rpd to crash and restart, resulting in a Denial of Service (DoS). Continued receipt and processing of this packet will create a sustained Denial of Service (DoS) condition.

This issue only affects systems configured in either of two ways:

1. systems with BGP traceoptions enabled
2. systems with BGP family traffic-engineering (BGP-LS) configured

and can be exploited from a directly connected and configured BGP peer. 

This issue affects iBGP and eBGP with any address family configured, and both IPv4 and IPv6 are affected by this vulnerability.

This issue affects:

Junos OS: 

• from 21.4 before 21.4R3-S9, 
• from 22.2 before 22.2R3-S5, 
• from 22.3 before 22.3R3-S4, 
• from 22.4 before 22.4R3-S5, 
• from 23.2 before 23.2R2-S3, 
• from 23.4 before 23.4R2-S3, 
• from 24.2 before 24.2R1-S2, 24.2R2; 

Junos OS Evolved: 

• from 21.4-EVO before 21.4R3-S9-EVO, 
• from 22.2-EVO before 22.2R3-S5-EVO, 
• from 22.3-EVO before 22.3R3-S4-EVO, 
• from 22.4-EVO before 22.4R3-S5-EVO, 
• from 23.2-EVO before 23.2R2-S3-EVO, 
• from 23.4-EVO before 23.4R2-S2-EVO, 
• from 24.2-EVO before 24.2R1-S2-EVO, 24.2R2-EVO.

This issue does not affect versions of Junos OS prior to 21.3R1.
This issue does not affect versions of Junos OS Evolved prior to 21.3R1-EVO.

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

This issue was discovered during external security research.

This is a similar but different vulnerability than the issue reported as CVE-2024-39516.

The following software releases have been updated to resolve this specific issue:

Junos OS: 21.4R3-S9, 22.2R3-S5, 22.3R3-S4, 22.4R3-S5, 23.2R2-S3, 23.4R2-S3, 24.2R1-S2, 24.2R2, 24.4R1, and all subsequent releases.
Junos OS Evolved: 21.4R3-S9-EVO, 22.2R3-S5-EVO, 22.3R3-S4-EVO, 22.4R3-S5-EVO, 23.2R2-S3-EVO, 23.4R2-S2-EVO, 24.2R1-S2-EVO, 24.2R2-EVO, 24.4R1-EVO, and all subsequent releases.

This issue is being tracked as 1823612 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).

If BGP traceoptions are enabled and traffic engineering is not configured, disable BGP traceoptions if they are not being used for active troubleshooting.

2025-01-08: Initial Publication
2025-01-27: Clarified that versions prior to 21.3R1 and 21.3R1-EVO are unaffected.

• KB16613: Overview of the Juniper Networks SIRT Quarterly Security Bulletin Publication Process [juniper.net]
• KB16765: In which releases are vulnerabilities fixed? [juniper.net]
• KB16446: Common Vulnerability Scoring System (CVSS) and Juniper's Security Advisories [juniper.net]
• Report a Security Vulnerability - How to Contact the Juniper Networks Security Incident Response Team

Juniper SIRT would like to acknowledge and thank Craig Dods from Meta’s Infrastructure Security Engineering team for responsibly reporting this vulnerability.