title: Junos OS: SRX Series: An FPC memory leak can occur in an APBR scenario
description: A Missing Release of Memory after Effective Lifetime vulnerability in the Application Quality of Experience (appqoe) subsystem of the PFE of Juniper Networks Junos OS on SRX Series allows an unauthenticated network based attacker to cause a Denial of Service (DoS). Upon receiving specific traffic a memory leak will occur. Sustained processing of such specific traffic will eventually lead to an out of memory condition that prevents all services from continuing to function, and requires a manual restart to recover. A device is only vulnerable when advance(d) policy based routing (APBR) is configured and AppQoE (sla rule) is not configured for these APBR rules. This issue affects Juniper Networks Junos OS on SRX Series: 20.3 versions prior to 20.3R3-S2; 20.4 versions prior to 20.4R3-S2; 21.1 versions prior to 21.1R3; 21.2 versions prior to 21.2R2-S1, 21.2R3; 21.3 versions prior to 21.3R1-S2, 21.3R2. This issue does not affect Juniper Networks Junos OS versions prior to 20.3R1.
problem types: CWE-401 Missing Release of Memory after Effective Lifetime
affected:
{
platforms: SRX Series
product: Junos OS
vendor: Juniper Networks
versions:
lessThan: 20.3R1, status: unaffected, version: unspecified, versionType: custom
lessThan: 20.3R3-S2, status: affected, version: 20.3, versionType: custom
lessThan: 20.4R3-S2, status: affected, version: 20.4, versionType: custom
lessThan: 21.1R3, status: affected, version: 21.1, versionType: custom
lessThan: 21.2R2-S1, 21.2R3, status: affected, version: 21.2, versionType: custom
lessThan: 21.3R1-S2, 21.3R2, status: affected, version: 21.3, 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: 20.3R3-S2, 20.4R3-S2, 21.1R3, 21.2R2-S1, 21.2R3, 21.3R1-S2, 21.3R2, 21.4R1, and all subsequent releases.
workarounds: There are no viable workarounds for this issue.