CVE-2020-1660: Junos OS: MX Series: Receipt of specific packets can cause services card to restart when DNS filtering is configured.

Published Oct 16, 2020
·
Updated

When DNS filtering is enabled on Juniper Networks Junos MX Series with one of the following cards MS-PIC, MS-MIC or MS-MPC, an incoming stream of packets processed by the Multiservices PIC Management Daemon (mspmand) process, responsible for managing "URL Filtering service", may crash, causing the Services PIC to restart. While the Services PIC is restarting, all PIC services including DNS filtering service (DNS sink holing) will be bypassed until the Services PIC completes its boot process. This vulnerability might allow an attacker to cause an extended Denial of Service (DoS) attack against the device and to cause clients to be vulnerable to DNS based attacks by malicious DNS servers when they send DNS requests through the device. As a result, devices which were once protected by the DNS Filtering service are no longer protected and at risk of exploitation. This issue affects Juniper Networks Junos OS: 17.3 versions prior to 17.3R3-S8; 18.3 versions prior to 18.3R3-S1; 18.4 versions prior to 18.4R3; 19.1 versions prior to 19.1R3; 19.2 versions prior to 19.2R2; 19.3 versions prior to 19.3R3. This issue does not affect Juniper Networks Junos OS 17.4, 18.1, and 18.2.

Affected Software

56 affected components
Juniper Junos=17.3
Juniper Junos=17.3-r1-s1
Juniper Junos=17.3-r2
Juniper Junos=17.3-r2-s1
Juniper Junos=17.3-r2-s2
Juniper Junos=17.3-r2-s3
Juniper Junos=17.3-r2-s4
Juniper Junos=17.3-r2-s5
Juniper Junos=17.3-r3
Juniper Junos=17.3-r3-s1
Juniper Junos=17.3-r3-s2
Juniper Junos=17.3-r3-s3
Juniper Junos=17.3-r3-s4
Juniper Junos=17.3-r3-s7
Juniper Junos=18.3
Juniper Junos=18.3-r1
Juniper Junos=18.3-r1-s1
Juniper Junos=18.3-r1-s2
Juniper Junos=18.3-r1-s3
Juniper Junos=18.3-r1-s5
Juniper Junos=18.3-r1-s6
Juniper Junos=18.3-r2
Juniper Junos=18.3-r2-s1
Juniper Junos=18.3-r2-s2
Juniper Junos=18.3-r2-s3
Juniper Junos=18.3-r3
Juniper Junos=18.4
Juniper Junos=18.4-r1
Juniper Junos=18.4-r1-s1
Juniper Junos=18.4-r1-s2
Juniper Junos=18.4-r1-s5
Juniper Junos=18.4-r1-s6
Juniper Junos=18.4-r2
Juniper Junos=18.4-r2-s1
Juniper Junos=18.4-r2-s2
Juniper Junos=18.4-r2-s3
Juniper Junos=18.4-r2-s4
Juniper Junos=19.1
Juniper Junos=19.1-r1
Juniper Junos=19.1-r1-s1
Juniper Junos=19.1-r1-s2
Juniper Junos=19.1-r1-s3
Juniper Junos=19.1-r1-s4
Juniper Junos=19.1-r2
Juniper Junos=19.1-r2-s1
Juniper Junos=19.2
Juniper Junos=19.2-r1
Juniper Junos=19.2-r1-s1
Juniper Junos=19.2-r1-s2
Juniper Junos=19.2-r1-s3
Juniper Junos=19.3
Juniper Junos=19.3-r1
Juniper Junos=19.3-r1-s1
Juniper Junos=19.3-r2
Juniper Junos=19.3-r2-s1
Juniper Junos=19.3-r2-s2

Remediation

Information

The following software releases have been updated to resolve this specific issue: Junos OS 17.3R3-S8, 18.3R3-S1, 18.4R3, 19.1R3, 19.2R2, 19.3R3, 19.4R1 and all subsequent releases.

Event History

Oct 16, 2020
CVE Published
via MITRE·08:31 PM
Data Sourced
via MITRE·08:31 PM
RemedyDescriptionSeverityWeakness

Frequently Asked Questions

1

What is the severity of CVE-2020-1660?

CVE-2020-1660 is rated as a High severity vulnerability primarily affecting Junos versions 17.3, 18.3, 18.4, and 19.1.

2

How do I fix CVE-2020-1660?

To fix CVE-2020-1660, it is recommended to upgrade to a patched version of Junos that addresses the vulnerability.

3

Which versions of Junos are affected by CVE-2020-1660?

Affected versions of Junos include 17.3, 18.3, 18.4, and 19.1, along with their respective minor updates.

4

What impact does CVE-2020-1660 have on my network?

CVE-2020-1660 can lead to a denial of service condition, causing the URL Filtering service to crash.

5

Is there a workaround for CVE-2020-1660?

There is no official workaround for CVE-2020-1660, so upgrading to a secure version is essential.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203