title: Junos OS: EX4300 Series: High CPU load due to receipt of specific IPv4 packets
description: 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.
problem types: CWE-400 Uncontrolled Resource Consumption
affected:
{
platforms: EX4300 series
product: Junos OS
vendor: Juniper Networks
versions:
lessThan: 17.3R3-S9, status: affected, version: 17.3, versionType: custom
lessThan: 17.4R2-S11, 17.4R3-S2, status: affected, version: 17.4, versionType: custom
lessThan: 18.1R3-S10, status: affected, version: 18.1, versionType: custom
lessThan: 18.2R3-S4, status: affected, version: 18.2, versionType: custom
lessThan: 18.3R2-S4, 18.3R3-S2, status: affected, version: 18.3, versionType: custom
lessThan: 18.4R2-S4, 18.4R3-S2, status: affected, version: 18.4, versionType: custom
lessThan: 19.1R2-S2, 19.1R3-S1, status: affected, version: 19.1, versionType: custom
lessThan: 19.2R1-S5, 19.2R2-S1, 19.2R3, status: affected, version: 19.2, versionType: custom
lessThan: 19.3R2-S4, 19.3R3, status: affected, version: 19.3, versionType: custom
lessThan: 19.4R1-S3, 19.4R2, status: affected, version: 19.4, versionType: custom
lessThan: 20.1R1-S3, 20.1R2, status: affected, version: 20.1, versionType: custom
}
metrics:
cvssV3_1: [
attackComplexity: LOW
attackVector: ADJACENT_NETWORK
availabilityImpact: HIGH
baseScore: 6.5
baseSeverity: MEDIUM
confidentialityImpact: NONE
integrityImpact: NONE
privilegesRequired: NONE
scope: UNCHANGED
userInteraction: NONE
vectorString: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
version: 3.1
]
exploits: Juniper SIRT is not aware of any malicious exploitation of this vulnerability.
solutions: The following software releases have been updated to resolve this specific issue: 17.3R3-S9, 17.4R2-S11, 17.4R3-S2, 18.1R3-S10, 18.2R3-S4, 18.3R2-S4, 18.3R3-S2, 18.4R2-S4, 18.4R3-S2, 19.1R2-S2, 19.1R3-S1, 19.2R1-S5, 19.2R2-S1, 19.2R3, 19.3R2-S4, 19.3R3, 19.4R1-S3, 19.4R2, 20.1R1-S3, 20.1R2, 20.2R1 and all subsequent releases.
workarounds: There are no viable workarounds for this issue.