title: Junos OS: SRX1500: Denial of service due to crash of srxpfe process under heavy traffic conditions.
description: Under certain heavy traffic conditions srxpfe process can crash and result in a denial of service condition for the SRX1500 device. Repeated crashes of the srxpfe can result in an extended denial of service condition. The SRX device may fail to forward traffic when this condition occurs. Affected releases are Juniper Networks Junos OS: 15.1X49 versions prior to 15.1X49-D170 on SRX1500; 17.3 versions prior to 17.3R3-S7 on SRX1500; 17.4 versions prior to 17.4R2-S8, 17.4R3 on SRX1500; 18.1 versions prior to 18.1R3-S8 on SRX1500; 18.2 versions prior to 18.2R3 on SRX1500; 18.3 versions prior to 18.3R2 on SRX1500; 18.4 versions prior to 18.4R2 on SRX1500.
problem types: Denial of Service
affected:
{
platforms: SRX1500
product: Junos OS
vendor: Juniper Networks
versions:
lessThan: 15.1X49-D170, status: affected, version: 15.1X49, versionType: custom
lessThan: 17.3R3-S7 (pending), status: affected, version: 17.3, versionType: custom
lessThan: 17.4R2-S8, 17.4R3, status: affected, version: 17.4, versionType: custom
lessThan: 18.1R3-S8, status: affected, version: 18.1, versionType: custom
lessThan: 18.2R3, status: affected, version: 18.2, versionType: custom
lessThan: 18.3R2, status: affected, version: 18.3, versionType: custom
lessThan: 18.4R2, status: affected, version: 18.4, 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: 15.1X49-D170, 17.3R3-S7(pending), 17.4R2-S8, 17.4R3, 18.1R3-S8, 18.2R3, 18.3R2, 18.4R2, 19.1R1, and all subsequent releases.
workarounds: There are no viable workarounds for this issue.