CVE-2020-1645

Junos OS: MX Series: Services card might restart when DNS filtering is enabled

HIGH
8.3
CVSS Score
Published: July 17, 2020 at 06:40 PM UTC
Updated: June 17, 2026 at 03:02 AM UTC
1 product affected across 1 vendorJunos

Using Junos OS by Juniper Networks?

Get instant alerts when new vulnerabilities affect Junos OS - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.3
Exploit prediction
EPSS 0.6%

Description

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. If the issue occurs, system core-dumps output will show a crash of mspmand process: root@device> show system core-dumps -rw-rw---- 1 nobody wheel 575685123 <Date> /var/tmp/pics/mspmand.core.<*>.gz This issue affects Juniper Networks Junos OS: 17.3 versions prior to 17.3R3-S8; 18.3 versions prior to 18.3R2-S4, 18.3R3-S1; 18.4 versions prior to 18.4R2-S5, 18.4R3; 19.1 versions prior to 19.1R2-S2, 19.1R3; 19.2 versions prior to 19.2R1-S5, 19.2R2; 19.3 versions prior to 19.3R2-S3, 19.3R3; 19.4 versions prior to 19.4R1-S3, 19.4R2. This issue does not affect Juniper Networks Junos OS releases prior to 17.3R2.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Vendor states this is fixed in 17.3R2 (unaffected)
Affected range stops below 17.3R3-S8, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 17.4 (unaffected)
Vendor states this is fixed in 18.1 (unaffected)
Vendor states this is fixed in 18.2 (unaffected)
Affected range stops below 18.3R2-S4, 18.3R3-S1, so it looks safe — our inference, not a vendor statement
Affected range stops below 18.4R2-S5, 18.4R3, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.1R2-S2, 19.1R3, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.2R1-S5, 19.2R2, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.3R2-S3, 19.3R3, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.4R1-S3, 19.4R2, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (1)

x_refsource_CONFIRMVendor Advisory
https://kb.juniper.net/JSA11028

CVSS

8.3HIGHjuniper
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
CHANGED
Confidentiality
LOW
Integrity
LOW
Availability
LOW
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-362NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card