title: Junos OS: A specific SNMP command can trigger a high CPU usage Denial of Service in the RPD daemon.
description: In a Point-to-Multipoint (P2MP) Label Switched Path (LSP) scenario, an uncontrolled resource consumption vulnerability in the Routing Protocol Daemon (RPD) in Juniper Networks Junos OS allows a specific SNMP request to trigger an infinite loop causing a high CPU usage Denial of Service (DoS) condition. This issue affects both SNMP over IPv4 and IPv6. This issue affects: Juniper Networks Junos OS: 12.3X48 versions prior to 12.3X48-D90; 15.1 versions prior to 15.1R7-S6; 15.1X49 versions prior to 15.1X49-D200; 15.1X53 versions prior to 15.1X53-D238, 15.1X53-D592; 16.1 versions prior to 16.1R7-S5; 16.2 versions prior to 16.2R2-S11; 17.1 versions prior to 17.1R3-S1; 17.2 versions prior to 17.2R3-S2; 17.3 versions prior to 17.3R3-S7; 17.4 versions prior to 17.4R2-S4, 17.4R3; 18.1 versions prior to 18.1R3-S5; 18.2 versions prior to 18.2R3; 18.2X75 versions prior to 18.2X75-D50; 18.3 versions prior to 18.3R2; 18.4 versions prior to 18.4R2; 19.1 versions prior to 19.1R2.
problem types: CWE-400 Uncontrolled Resource Consumption
affected:
{
product: Junos OS
vendor: Juniper Networks
versions:
lessThan: 12.3X48-D90, status: affected, version: 12.3X48, versionType: custom
lessThan: 15.1X53-D238, 15.1X53-D592, status: affected, version: 15.1X53, versionType: custom
lessThan: 16.1R7-S5, status: affected, version: 16.1, versionType: custom
lessThan: 16.2R2-S11, status: affected, version: 16.2, versionType: custom
lessThan: 17.1R2-S11, 17.1R3-S1, status: affected, version: 17.1, versionType: custom
lessThan: 17.2R3-S2, status: affected, version: 17.2, versionType: custom
lessThan: 17.3R3-S7, status: affected, version: 17.3, versionType: custom
lessThan: 17.4R2-S4, 17.4R3, status: affected, version: 17.4, versionType: custom
lessThan: 18.1R3-S5, status: affected, version: 18.1, versionType: custom
lessThan: 18.2R3, status: affected, version: 18.2, versionType: custom
lessThan: 18.2X75-D50, status: affected, version: 18.2X75, versionType: custom
lessThan: 18.3R2, status: affected, version: 18.3, versionType: custom
lessThan: 18.4R2, status: affected, version: 18.4, versionType: custom
lessThan: 19.1R2, status: affected, version: 19.1, versionType: custom
lessThan: 19.2R1, status: affected, version: 19.2, versionType: custom
lessThan: 15.1X49-D200, status: affected, version: 15.1X49, versionType: custom
lessThan: 15.1R7-S6, status: affected, version: 15.1, versionType: custom
}
metrics:
cvssV3_1: [
attackComplexity: LOW
attackVector: NETWORK
availabilityImpact: HIGH
baseScore: 6.5
baseSeverity: MEDIUM
confidentialityImpact: NONE
integrityImpact: NONE
privilegesRequired: LOW
scope: UNCHANGED
userInteraction: NONE
vectorString: CVSS:3.1/AV:N/AC:L/PR:L/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: 12.3X48-D90, 15.1X49-D200, 15.1R7-S6, 15.1X53-D238, 15.1X53-D592, 16.1R7-S5, 16.2R2-S11, 17.1R3-S1, 17.2R3-S2, 17.3R3-S7, 17.4R2-S4, 17.4R3, 18.1R3-S5, 18.2R3, 18.2X75-D50, 18.3R2, 18.4R2, 19.1R2, 19.2R1, and all subsequent releases.
workarounds: If SNMP is not needed, remove SNMP from the system, otherwise, there are no available workarounds for this issue.  SNMP is disabled by default.
Additional steps which may reduce the risk of exploitation include:
Utilizing edge filtering with source-address validation (uRPF, etc.), access control lists (ACLs), and/or SNMPv3 authentication to limit access to the device only from trusted hosts.