title: Junos OS: QFX10K Series: An ICCP flap will be observed due to excessive specific traffic
description:
An Allocation of Resources Without Limits or Throttling vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS allows a network-based, unauthenticated attacker to cause a Denial of Service (DoS).
On QFX10K Series, Inter-Chassis Control Protocol (ICCP) is used in MC-LAG topologies to exchange control information between the devices in the topology. ICCP connection flaps and sync issues will be observed due to excessive specific traffic to the local device.
This issue affects Juniper Networks Junos OS on QFX10K Series:
*  All versions prior to 20.2R3-S7;
*  20.4 versions prior to 20.4R3-S4;
*  21.1 versions prior to 21.1R3-S3;
*  21.2 versions prior to 21.2R3-S1;
*  21.3 versions prior to 21.3R3;
*  21.4 versions prior to 21.4R3;
*  22.1 versions prior to 22.1R2.
problem types: CWE-770 Allocation of Resources Without Limits or Throttling
affected:
{
defaultStatus: unaffected
platforms: QFX10K Series
product: Junos OS
vendor: Juniper Networks
versions:
lessThan: 20.2R3-S7, status: affected, version: unspecified, versionType: custom
lessThan: 20.4R3-S4, status: affected, version: 20.4, versionType: custom
lessThan: 21.1R3-S3, status: affected, version: 21.1, versionType: custom
lessThan: 21.2R3-S1, status: affected, version: 21.2, versionType: custom
lessThan: 21.3R3, status: affected, version: 21.3, versionType: custom
lessThan: 21.4R3, status: affected, version: 21.4, versionType: custom
lessThan: 22.1R2, status: affected, version: 22.1, 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
]
format: CVSS
scenarios: GENERAL
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: 20.2R3-S7, 20.4R3-S4, 21.1R3-S3, 21.2R3-S1, 21.3R3, 21.4R3, 22.1R2, 22.2R1, and all subsequent releases.
workarounds: There are no known workarounds for this issue.