BGP packets can trigger rpd crash when BGP tracing is enabled.
Juniper Networks Junos OS
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Juniper Networks Junos OS |
|
|
Juniper Networks Junos OS
| Product | Affected | Fixed in |
|---|---|---|
| Juniper Networks Junos OS |
|
|
When BGP tracing is enabled an incoming BGP message may cause the Junos OS routing protocol daemon (rpd) process to crash and restart. While rpd restarts after a crash, repeated crashes can result in an extended DoS condition. Affected releases are Juniper Networks Junos OS: 16.1 versions prior to 16.1R7-S4, 16.1R7-S5; 16.2 versions prior to 16.2R2-S9, 16.2R3; 17.1 versions prior to 17.1R3; 17.2 versions prior to 17.2R3-S1; 17.3 versions prior to 17.3R3-S3, 17.3R3-S4, 17.3R4; 17.4 versions prior to 17.4R1-S7, 17.4R2-S3, 17.4R2-S4, 17.4R3; 18.1 versions prior to 18.1R2-S4, 18.1R3-S4, 18.1R4; 18.2 versions prior to 18.2R2-S2, 18.2R2-S3, 18.2R3; 18.2X75 versions prior to 18.2X75-D40; 18.3 versions prior to 18.3R1-S3, 18.3R2; 18.4 versions prior to 18.4R1-S2, 18.4R2. This issue does not affect Junos releases prior to 16.1R1.
From the CVE record · juniper
When BGP tracing is enabled, an incoming BGP message can crash and restart the Junos OS routing protocol daemon (rpd). Repeated crashes can cause an extended denial of service. The input does not specify whether authentication is required; no user interaction is described.
Operators running Juniper Networks Junos OS 16.1 through 18.4 should check the affected release ranges; releases prior to 16.1R1 are not affected.