title: Junos OS and Junos OS Evolved: In Point to MultiPoint (P2MP) scenarios receipt of various crafted packets causes RPD to core.
description: In Point to MultiPoint (P2MP) scenarios within established sessions between network or adjacent neighbors the improper use of a source to destination copy write operation combined with a Stack-based Buffer Overflow on certain specific packets processed by the routing protocol daemon (RPD) of Juniper Networks Junos OS and Junos OS Evolved sent by a remote unauthenticated network attacker causes the RPD to crash causing a Denial of Service (DoS). Continued receipt and processing of these packets will create a sustained Denial of Service (DoS) condition. This issue affects: Juniper Networks Junos OS 19.2 versions prior to 19.2R3-S2; 19.3 versions prior to 19.3R2-S6, 19.3R3-S2; 19.4 versions prior to 19.4R1-S4, 19.4R2-S4, 19.4R3-S3; 20.1 versions prior to 20.1R2-S2, 20.1R3; 20.2 versions prior to 20.2R2-S3, 20.2R3; 20.3 versions prior to 20.3R2. This issue does not affect Juniper Networks Junos OS versions prior to 19.2R1. Juniper Networks Junos OS Evolved 20.1 versions prior to 20.1R3-EVO; 20.2 versions prior to 20.2R3-EVO; 20.3 versions prior to 20.3R2-EVO.
problem types: improper usage of a source to destination copy write operation
affected:
{
product: Junos OS
vendor: Juniper Networks
versions:
lessThan: 19.2R1, status: unaffected, version: unspecified, versionType: custom
lessThan: 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.4R2-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.2R2-S3, 20.2R3, status: affected, version: 20.2, versionType: custom
lessThan: 20.3R2, status: affected, version: 20.3, versionType: custom
}
{
product: Junos OS Evolved
vendor: Juniper Networks
versions:
lessThan: 20.1R3-EVO, status: affected, version: 20.1, versionType: custom
lessThan: 20.2R3-EVO, status: affected, version: 20.2, versionType: custom
lessThan: 20.3R2-EVO, status: affected, version: 20.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:
Junos OS: 19.2R3-S2, 19.3R2-S6, 19.3R3-S2, 19.4R1-S4, 19.4R2-S4, 19.4R3-S3, 20.1R2-S2, 20.1R3, 20.2R2-S3, 20.2R3, 20.3R2, 20.4R1, and all subsequent releases.
Junos OS Evolved: 20.1R3-EVO, 20.2R3-EVO, 20.3R2-EVO, 20.4R1-EVO, and all subsequent releases.
workarounds: For Junos OS you can remove the traffic-statistics from the configuration to work around this issue.
[protoccols ldp traffic-statistics {sensor-based-stats;}]
For Junos OS Evolved there are no viable workarounds for this issue.