title: Junos OS: EX4300-MP, EX4600, QFX5000 Series: In VxLAN scenarios specific packets processed cause a memory leak leading to a PFE crash
description: In VxLAN scenarios on EX4300-MP, EX4600, QFX5000 Series devices an Uncontrolled Memory Allocation vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS allows an unauthenticated adjacently located attacker sending specific packets to cause a Denial of Service (DoS) condition by crashing one or more PFE's when they are received and processed by the device. Upon automatic restart of the PFE, continued processing of these packets will cause the memory leak to reappear. Depending on the volume of packets received the attacker may be able to create a sustained Denial of Service (DoS) condition. This issue affects: Juniper Networks Junos OS on EX4300-MP, EX4600, QFX5000 Series: 17.1 version 17.1R1 and later versions prior to 17.3R3-S12; 17.4 versions prior to 17.4R2-S13, 17.4R3-S5; 18.1 versions prior to 18.1R3-S13; 18.2 versions prior to 18.2R3-S8; 18.3 versions prior to 18.3R3-S5; 18.4 versions prior to 18.4R1-S8, 18.4R2-S6, 18.4R3-S6; 19.1 versions prior to 19.1R3-S4; 19.2 versions prior to 19.2R1-S7, 19.2R3-S1; 19.3 versions prior to 19.3R2-S6, 19.3R3-S1; 19.4 versions prior to 19.4R1-S4, 19.4R2-S4, 19.4R3-S1; 20.1 versions prior to 20.1R2; 20.2 versions prior to 20.2R2-S3, 20.2R3; 20.3 versions prior to 20.3R2. This issue does not affect Junos OS versions prior to 17.1R1.
problem types: CWE-789 Uncontrolled Memory Allocation
affected:
{
vendor: Juniper Networks
product: Junos OS
versions:
version: unspecified, lessThan: 17.1R1, status: unaffected, versionType: custom
version: 17.1R1, status: affected, lessThan: 17.1*, versionType: custom
version: 17.2R1, status: affected, lessThan: 17.2*, versionType: custom
version: 17.3, status: affected, lessThan: 17.3R3-S12, versionType: custom
version: 17.4, status: affected, lessThan: 17.4R2-S13, 17.4R3-S5, versionType: custom
version: 18.1, status: affected, lessThan: 18.1R3-S13, versionType: custom
version: 18.2, status: affected, lessThan: 18.2R3-S8, versionType: custom
version: 18.3, status: affected, lessThan: 18.3R3-S5, versionType: custom
version: 18.4, status: affected, lessThan: 18.4R1-S8, 18.4R2-S6, 18.4R3-S6, versionType: custom
version: 19.1, status: affected, lessThan: 19.1R3-S4, versionType: custom
version: 19.2, status: affected, lessThan: 19.2R1-S7, 19.2R3-S1, versionType: custom
version: 19.3, status: affected, lessThan: 19.3R2-S6, 19.3R3-S1, versionType: custom
version: 19.4, status: affected, lessThan: 19.4R1-S4, 19.4R2-S4, 19.4R3-S1, versionType: custom
version: 20.1, status: affected, lessThan: 20.1R2, versionType: custom
version: 20.2, status: affected, lessThan: 20.2R2-S3, 20.2R3, versionType: custom
version: 20.3, status: affected, lessThan: 20.3R2, versionType: custom
platforms: EX4300-MP, EX4600, QFX5000 Series
}
metrics:
cvssV3_1: [
version: 3.1
vectorString: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
attackVector: ADJACENT_NETWORK
attackComplexity: LOW
privilegesRequired: NONE
userInteraction: NONE
scope: UNCHANGED
confidentialityImpact: NONE
integrityImpact: NONE
availabilityImpact: HIGH
baseScore: 6.5
baseSeverity: MEDIUM
]
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-S12, 17.4R2-S13, 17.4R3-S5, 18.1R3-S13, 18.2R3-S8, 18.3R3-S5, 18.4R1-S8, 18.4R2-S6, 18.4R3-S6, 19.1R3-S4, 19.2R1-S7, 19.2R3-S1, 19.3R2-S6, 19.3R3-S1, 19.4R1-S4, 19.4R2-S4, 19.4R3-S1, 20.1R2, 20.2R2-S3, 20.2R3, 20.3R2, 20.4R1, and all subsequent releases.
workarounds: There are no viable workarounds for this issue.