CVE-2020-1600

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.

Remediation

Solution:

  • 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.

Workaround:

  • 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.

Categories

6.5
CVSS
Severity: Medium
CVSS 3.1 •
CVSS 2.0 •
EPSS 0.22%
Vendor Advisory juniper.net
Affected: Juniper Networks Junos OS
Published at:
Updated at:

References

Link Tags
https://prsearch.juniper.net/InfoCenter/index?page=prcontent&id=PR1402185 permissions required
https://kb.juniper.net/JSA10979 vendor advisory

Frequently Asked Questions

What is the severity of CVE-2020-1600?
CVE-2020-1600 has been scored as a medium severity vulnerability.
How to fix CVE-2020-1600?
To fix CVE-2020-1600: 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.
Is CVE-2020-1600 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2020-1600 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2020-1600?
CVE-2020-1600 affects Juniper Networks Junos OS.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.