On Juniper Networks Junos OS and Junos OS Evolved devices, processing a specific UPDATE for an EBGP peer can lead to a routing process daemon (RPD) crash and restart. This issue occurs only when the device is receiving and processing the BGP UPDATE for an EBGP peer. This issue does not occur when the device is receiving and processing the BGP UPDATE for an IBGP peer. However, the offending BGP UPDATE can originally come from an EBGP peer, propagates through the network via IBGP peers without causing crash, then it causes RPD crash when it is processed for a BGP UPDATE towards an EBGP peer. Repeated receipt and processing of the same specific BGP UPDATE can result in an extended Denial of Service (DoS) condition. This issue affects: Juniper Networks Junos OS: 17.3R3-S6, 17.4R2-S7, and 18.1R3-S7. Juniper Networks Junos OS Evolved 19.2R2-EVO and later versions, prior to 19.3R1-EVO. Other Junos OS releases are not affected.
Summary
AIA specific BGP UPDATE processed for an EBGP peer can crash and restart the routing process daemon (RPD). Repeated processing can cause extended denial of service. The UPDATE can reach the device over the network, including via IBGP peers, but processing it for an IBGP peer does not trigger the crash.
Who should check
Operators running Junos OS 17.3R3-S6, 17.4R2-S7, or 18.1R3-S7, or Junos OS Evolved versions from 19.2R2-EVO up to but not including 19.3R1-EVO, should check their devices.
What to do
- 1Consult the Juniper advisory for the applicable fix.
- 2Update affected devices according to the advisory.