title: Junos OS: Upon receipt of certain types of malformed PCEP packets the pccd process may crash.
description: Certain types of malformed Path Computation Element Protocol (PCEP) packets when received and processed by a Juniper Networks Junos OS device serving as a Path Computation Client (PCC) in a PCEP environment using Juniper's path computational element protocol daemon (pccd) process allows an attacker to cause the pccd process to crash and generate a core file thereby causing a Denial of Service (DoS). Continued receipt of this family of malformed PCEP packets will cause an extended Denial of Service (DoS) condition. This issue affects: Juniper Networks Junos OS: 15.1 versions prior to 15.1F6-S13, 15.1R7-S4; 15.1X49 versions prior to 15.1X49-D180 on SRX Series; 15.1X53 versions prior to 15.1X53-D238, 15.1X53-D496, 15.1X53-D592; 16.1 versions prior to 16.1R7-S4; 16.2 versions prior to 16.2R2-S9; 17.1 versions prior to 17.1R2-S11, 17.1R3; 17.2 versions prior to 17.2R1-S9; 17.2 version 17.2R2 and later prior to 17.2R3-S2; 17.3 versions prior to 17.3R3-S3; 17.4 versions prior to 17.4R2-S2, 17.4R3; 18.1 versions prior to 18.1R3-S2; 18.2 versions prior to 18.2R2-S6, 18.2R3; 18.2X75 versions prior to 18.2X75-D40; 18.3 versions prior to 18.3R2; 18.4 versions prior to 18.4R1-S2, 18.4R2. This issue does not affect releases of Junos OS prior to 15.1R1.
problem types: Denial of Service (DoS)
affected:
{
product: Junos OS
vendor: Juniper Networks
versions:
lessThan: 15.1F6-S13, 15.1R7-S4, status: affected, version: 15.1, versionType: custom
lessThan: 16.1R7-S4, status: affected, version: 16.1, versionType: custom
lessThan: 16.2R2-S9, status: affected, version: 16.2, versionType: custom
lessThan: 17.1R2-S11, 17.1R3, status: affected, version: 17.1, versionType: custom
changes: [at: 17.2R2, status: affected], lessThan: 17.2R1-S9, 17.2R3-S2, status: affected, version: 17.2, versionType: custom
lessThan: 17.3R3-S3, status: affected, version: 17.3, versionType: custom
lessThan: 17.4R2-S2, 17.4R3, status: affected, version: 17.4, versionType: custom
lessThan: 18.1R3-S2, status: affected, version: 18.1, versionType: custom
lessThan: 18.2R3, status: affected, version: 18.2, versionType: custom
lessThan: 18.2X75-D40, status: affected, version: 18.2X75, versionType: custom
lessThan: 18.2R2-S6, 18.3R2, status: affected, version: 18.3, versionType: custom
lessThan: 18.4R1-S2, 18.4R2, status: affected, version: 18.4, versionType: custom
lessThan: 15.1X53-D238, 15.1X53-D496, 15.1X53-D592, status: affected, version: 15.1X53, versionType: custom
}
{
platforms: SRX Series
product: Junos OS
vendor: Juniper Networks
versions:
lessThan: 15.1X49-D180, status: affected, version: 15.1X49, versionType: custom
}
metrics:
cvssV3_1: [
attackComplexity: LOW
attackVector: NETWORK
availabilityImpact: LOW
baseScore: 5.3
baseSeverity: MEDIUM
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:L
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.1F6-S13, 15.1R7-S4, 15.1X49-D180, 15.1X53-D238, 15.1X53-D496, 15.1X53-D592, 16.1R7-S4, 16.2R2-S9, 17.1R2-S11, 17.1R3, 17.2R1-S9, 17.2R3-S2, 17.3R3-S3, 17.4R2-S2, 17.4R2-S4, 17.4R3, 18.1R3-S2, 18.2R2-S6, 18.2R3, 18.2X75-D40, 18.3R2, 18.4R1-S2, 18.4R2, 19.1R1, and all subsequent releases.
workarounds: There are no viable workarounds for this issue.