title: Junos OS: Specific packets over VXLAN cause FPC memory leak and ultimately reset
description: A Missing Release of Resource after Effective Lifetime vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS allows an unauthenticated networked attacker to cause a Denial of Service (DoS) by sending specific packets over VXLAN which cause heap memory to leak and on exhaustion the PFE to reset. The heap memory utilization can be monitored with the command: user@host> show chassis fpc This issue affects: Juniper Networks Junos OS 19.4 versions prior to 19.4R2-S6, 19.4R3-S6; 20.1 versions prior to 20.1R3-S2; 20.2 versions prior to 20.2R3-S3; 20.3 versions prior to 20.3R3-S1; 20.4 versions prior to 20.4R3; 21.1 versions prior to 21.1R3; 21.2 versions prior to 21.2R2. This issue does not affect versions of Junos OS prior to 19.4R1.
problem types: Denial of Service (DoS)
affected:
{
product: Junos OS
vendor: Juniper Networks
versions:
lessThan: 19.4R1, status: unaffected, version: unspecified, versionType: custom
lessThan: 19.4R2-S6, 19.4R3-S6, status: affected, version: 19.4, versionType: custom
lessThan: 20.1R3-S2, status: affected, version: 20.1, versionType: custom
lessThan: 20.2R3-S3, status: affected, version: 20.2, versionType: custom
lessThan: 20.3R3-S1, status: affected, version: 20.3, versionType: custom
lessThan: 20.4R3, status: affected, version: 20.4, versionType: custom
lessThan: 21.1R3, status: affected, version: 21.1, versionType: custom
lessThan: 21.2R2, status: affected, version: 21.2, versionType: custom
}
metrics:
cvssV3_1: [
attackComplexity: LOW
attackVector: NETWORK
availabilityImpact: HIGH
baseScore: 7.5
baseSeverity: HIGH
confidentialityImpact: NONE
integrityImpact: NONE
privilegesRequired: NONE
scope: UNCHANGED
userInteraction: NONE
vectorString: CVSS:3.1/AV:N/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 Junos OS software releases have been updated to resolve this specific issue: 19.4R2-S6, 19.4R3-S6, 20.1R3-S2, 20.2R3-S3, 20.3R3-S1, 20.4R3, 21.1R3, 21.2R2, 21.3R1, and all subsequent releases.
workarounds: There are no viable workarounds for this issue.