Junos OS: EX4300 Series: High CPU load due to receipt of specific IPv4 packets
Juniper Networks Junos OS
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Juniper Networks Junos OS EX4300 series |
| No fix yet |
Juniper Networks Junos OS
| Product | Affected | Fixed in |
|---|---|---|
| Juniper Networks Junos OS EX4300 series |
| No fix yet |
On Juniper Networks EX4300 Series, receipt of a stream of specific IPv4 packets can cause Routing Engine (RE) high CPU load, which could lead to network protocol operation issue and traffic interruption. This specific packets can originate only from within the broadcast domain where the device is connected. This issue occurs when the packets enter to the IRB interface. Only IPv4 packets can trigger this issue. IPv6 packets cannot trigger this issue. This issue affects Juniper Networks Junos OS on EX4300 series: 17.3 versions prior to 17.3R3-S9; 17.4 versions prior to 17.4R2-S11, 17.4R3-S2; 18.1 versions prior to 18.1R3-S10; 18.2 versions prior to 18.2R3-S4; 18.3 versions prior to 18.3R2-S4, 18.3R3-S2; 18.4 versions prior to 18.4R2-S4, 18.4R3-S2; 19.1 versions prior to 19.1R2-S2, 19.1R3-S1; 19.2 versions prior to 19.2R1-S5, 19.2R2-S1, 19.2R3; 19.3 versions prior to 19.3R2-S4, 19.3R3; 19.4 versions prior to 19.4R1-S3, 19.4R2; 20.1 versions prior to 20.1R1-S3, 20.1R2.
From the CVE record · juniper
On EX4300 Series devices, specific IPv4 packets entering an IRB interface can drive Routing Engine CPU usage high, potentially disrupting network protocols and interrupting traffic. The packets must originate within the device’s broadcast domain; the input does not specify authentication or user-interaction requirements. IPv6 packets do not trigger the issue.
Operators of Junos OS on EX4300 Series devices should check affected 17.3, 17.4, 18.1–18.4, 19.1–19.4, and 20.1 releases below the applicable fixed version.