title: Junos OS Evolved: PTX Series: An attacker can cause a kernel panic by sending a malformed TCP packet to the device
description: An Improper Validation of Syntactic Correctness of Input vulnerability in the kernel of Juniper Networks Junos OS Evolved on PTX series allows a network-based, unauthenticated attacker to cause a Denial of Service (DoS). When an incoming TCP packet destined to the device is malformed there is a possibility of a kernel panic. Only TCP packets destined to the ports for BGP, LDP and MSDP can trigger this. This issue only affects PTX10004, PTX10008, PTX10016. No other PTX Series devices or other platforms are affected. This issue affects Juniper Networks Junos OS Evolved: 20.4-EVO versions prior to 20.4R3-S4-EVO; 21.3-EVO versions prior to 21.3R3-EVO; 21.4-EVO versions prior to 21.4R3-EVO; 22.1-EVO versions prior to 22.1R2-EVO. This issue does not affect Juniper Networks Junos OS Evolved versions prior to 20.4R1-EVO.
problem types: Denial of Service (DoS)
affected:
{
vendor: Juniper Networks
product: Junos OS Evolved
versions:
version: unspecified, lessThan: 20.4R1-EVO, status: unaffected, versionType: custom
version: 20.4-EVO, status: affected, lessThan: 20.4R3-S4-EVO, versionType: custom
version: 21.3-EVO, status: affected, lessThan: 21.3R3-EVO, versionType: custom
version: 21.4-EVO, status: affected, lessThan: 21.4R3-EVO, versionType: custom
version: 22.1-EVO, status: affected, lessThan: 22.1R2-EVO, versionType: custom
platforms: PTX10004, PTX10008, PTX10016
}
metrics:
cvssV3_1: [
version: 3.1
vectorString: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
attackVector: NETWORK
attackComplexity: LOW
privilegesRequired: NONE
userInteraction: NONE
scope: UNCHANGED
confidentialityImpact: NONE
integrityImpact: NONE
availabilityImpact: HIGH
baseScore: 7.5
baseSeverity: HIGH
]
exploits: Juniper SIRT is not aware of any malicious exploitation of this vulnerability.
solutions: The following Junos OS Evolved software releases have been updated to resolve this specific issue: 20.4R3-S4-EVO, 21.4R3-EVO, 22.1R2-EVO, 22.2R1-EVO, and all subsequent releases.
workarounds: There are no known workarounds for this issue.