title: SRX Series and MX Series with SPC3: A high percentage of fragments might lead to high latency or packet drops
description: An Insufficient Algorithmic Complexity combined with an Allocation of Resources Without Limits or Throttling vulnerability in the flow processing daemon (flowd) of Juniper Networks Junos OS on SRX Series and MX Series with SPC3 allows an unauthenticated network attacker to cause latency in transit packet processing and even packet loss. If transit traffic includes a significant percentage (> 5%) of fragmented packets which need to be reassembled, high latency or packet drops might be observed. This issue affects Juniper Networks Junos OS on SRX Series, MX Series with SPC3: All versions prior to 18.2R3; 18.3 versions prior to 18.3R3; 18.4 versions prior to 18.4R2-S9, 18.4R3; 19.1 versions prior to 19.1R2; 19.2 versions prior to 19.2R1-S1, 19.2R2.
problem types: CWE-407 Algorithmic Complexity
affected:
{
platforms: SRX Series, MX Series with SPC3
product: Junos OS
vendor: Juniper Networks
versions:
lessThan: 18.2R3, status: affected, version: unspecified, versionType: custom
lessThan: 18.3R3, status: affected, version: 18.3, versionType: custom
lessThan: 18.4R2-S9, 18.4R3, status: affected, version: 18.4, versionType: custom
lessThan: 19.1R2, status: affected, version: 19.1, versionType: custom
lessThan: 19.2R1-S1, 19.2R2, status: affected, version: 19.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 software releases have been updated to resolve this specific issue: 18.2R3, 18.3R3, 18.4R2-S9, 18.4R3, 19.1R2, 19.2R1-S1, 19.2R2, 19.3R1, and all subsequent releases.
workarounds: There are no viable workarounds for this issue.