title: Junos OS: MX Series: Traffic drops will be observed if MS-MPC/MS-PIC resources are consumed by certain traffic causing a partial DoS
description: On MX Series platforms with MS-MPC/MS-MIC, an Allocation of Resources Without Limits or Throttling vulnerability in Juniper Networks Junos OS allows an unauthenticated network attacker to cause a partial Denial of Service (DoS) with a high rate of specific traffic. If a Class of Service (CoS) rule is attached to the service-set and a high rate of specific traffic is processed by this service-set, for some of the other traffic which has services applied and is being processed by this MS-MPC/MS-MIC drops will be observed. Continued receipted of this high rate of specific traffic will create a sustained Denial of Service (DoS) condition. This issue affects: Juniper Networks Junos OS on MX Series with MS-MPC/MS-MIC: All versions prior to 17.4R3-S5; 18.3 versions prior to 18.3R3-S5; 18.4 versions prior to 18.4R3-S9; 19.1 versions prior to 19.1R3-S6; 19.2 versions prior to 19.2R1-S7, 19.2R3-S3; 19.3 versions prior to 19.3R2-S7, 19.3R3-S3; 19.4 versions prior to 19.4R3-S5; 20.1 versions prior to 20.1R2-S2, 20.1R3-S1; 20.2 versions prior to 20.2R3-S2; 20.3 versions prior to 20.3R3; 20.4 versions prior to 20.4R2-S1, 20.4R3; 21.1 versions prior to 21.1R1-S1, 21.1R2.
problem types: CWE-770 Allocation of Resources Without Limits or Throttling
affected:
{
platforms: MX Series
product: Junos OS
vendor: Juniper Networks
versions:
lessThan: 17.4R3-S5, status: affected, version: unspecified, versionType: custom
lessThan: 18.3R3-S5, status: affected, version: 18.3, versionType: custom
lessThan: 18.4R3-S9, status: affected, version: 18.4, versionType: custom
lessThan: 19.1R3-S6, status: affected, version: 19.1, versionType: custom
lessThan: 19.2R1-S7, 19.2R3-S3, status: affected, version: 19.2, versionType: custom
lessThan: 19.3R2-S7, 19.3R3-S3, status: affected, version: 19.3, versionType: custom
lessThan: 19.4R3-S5, status: affected, version: 19.4, versionType: custom
lessThan: 20.1R2-S2, 20.1R3-S1, status: affected, version: 20.1, versionType: custom
lessThan: 20.2R3-S2, status: affected, version: 20.2, versionType: custom
lessThan: 20.3R3, status: affected, version: 20.3, versionType: custom
lessThan: 20.4R2-S1, 20.4R3, status: affected, version: 20.4, versionType: custom
lessThan: 21.1R1-S1, 21.1R2, status: affected, version: 21.1, versionType: custom
}
metrics:
cvssV3_1: [
attackComplexity: LOW
attackVector: NETWORK
availabilityImpact: LOW
baseScore: 5.3
baseSeverity: MEDIUM
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:L
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.4R3-S5, 18.3R3-S5, 18.4R3-S9, 19.1R3-S6, 19.2R1-S7, 19.2R3-S3, 19.3R2-S7, 19.3R3-S3, 19.4R3-S5, 20.1R2-S2, 20.1R3-S1, 20.2R3-S2, 20.3R3, 20.4R2-S1, 20.4R3, 21.1R1-S1, 21.1R2, 21.2R1, and all subsequent releases.
workarounds: There are no viable workarounds for this issue.