title: Junos OS: SRX Series: The flowd process will crash if log session-close is configured and specific traffic is received
description: An Improper Check for Unusual or Exceptional Conditions vulnerability combined with a Race Condition in the flow daemon (flowd) of Juniper Networks Junos OS on SRX300 Series, SRX500 Series, SRX1500, and SRX5000 Series with SPC2 allows an unauthenticated network based attacker sending specific traffic to cause a crash of the flowd/srxpfe process, responsible for traffic forwarding in SRX, which will cause a Denial of Service (DoS). Continued receipt and processing of this specific traffic will create a sustained Denial of Service (DoS) condition. This issue can only occur when specific packets are trying to create the same session and logging for session-close is configured as a policy action. Affected platforms are: SRX300 Series, SRX500 Series, SRX1500, and SRX5000 Series with SPC2. Not affected platforms are: SRX4000 Series, SRX5000 Series with SPC3, and vSRX Series. This issue affects Juniper Networks Junos OS SRX300 Series, SRX500 Series, SRX1500, and SRX5000 Series with SPC2: 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-S2; 19.3 versions prior to 19.3R2-S6, 19.3R3-S2; 19.4 versions prior to 19.4R1-S4, 19.4R3-S3; 20.1 versions prior to 20.1R2-S2, 20.1R3; 20.2 versions prior to 20.2R3; 20.3 versions prior to 20.3R2-S1, 20.3R3; 20.4 versions prior to 20.4R2.
problem types: CWE-754 Improper Check for Unusual or Exceptional Conditions
affected:
{
platforms: SRX300 Series, SRX500 Series, SRX1500, and SRX5000 Series with SPC2
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-S2, status: affected, version: 19.2, versionType: custom
lessThan: 19.3R2-S6, 19.3R3-S2, status: affected, version: 19.3, versionType: custom
lessThan: 19.4R1-S4, 19.4R3-S3, status: affected, version: 19.4, versionType: custom
lessThan: 20.1R2-S2, 20.1R3, status: affected, version: 20.1, versionType: custom
lessThan: 20.2R3, status: affected, version: 20.2, versionType: custom
lessThan: 20.3R2-S1, 20.3R3, status: affected, version: 20.3, versionType: custom
lessThan: 20.4R2, status: affected, version: 20.4, versionType: custom
}
metrics:
cvssV3_1: [
attackComplexity: HIGH
attackVector: NETWORK
availabilityImpact: HIGH
baseScore: 5.9
baseSeverity: MEDIUM
confidentialityImpact: NONE
integrityImpact: NONE
privilegesRequired: NONE
scope: UNCHANGED
userInteraction: NONE
vectorString: CVSS:3.1/AV:N/AC:H/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: 17.4R3-S5, 18.3R3-S5, 18.4R3-S9, 19.1R3-S6, 19.2R1-S7, 19.2R3-S2, 19.3R2-S6, 19.3R3-S2, 19.4R1-S4, 19.4R3-S3, 20.1R2-S2, 20.1R3, 20.2R3, 20.3R2-S1, 20.3R3, 20.4R2, 21.1R1, and all subsequent releases.
workarounds: Please remove the session-close log action from the policy actions of all policies.