Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2020-1645

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

High8.3EPSS 0.63%
Published
Updated
Reserved
Assigned by
juniper

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.

Scores

CVSS scores of CVE-2020-1645, by who scored it
Scored byCVSSScoreVector
juniperCNA (assigner)3.1High8.3CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L
NVDNVD · Modified3.1High8.3CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L
EPSS (exploitation in 30 days)
0.63% · top 50% of all CVEs (6 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.3.

Weakness

Affected products

  • Juniper Networks · Junos OS

    • unaffected unspecified – < 17.3R2
    • unaffected 17.4
    • unaffected 18.1
    • unaffected 18.2
    • affected 17.3 – < 17.3R3-S8
    • affected 18.3 – < 18.3R2-S4, 18.3R3-S1
    • affected 18.4 – < 18.4R2-S5, 18.4R3
    • affected 19.1 – < 19.1R2-S2, 19.1R3
    • affected 19.2 – < 19.2R1-S5, 19.2R2
    • affected 19.3 – < 19.3R2-S3, 19.3R3
    • affected 19.4 – < 19.4R1-S3, 19.4R2

What to do

Solution: The following software releases have been updated to resolve this specific issue: 18.3R2-S4, 18.3R3-S1, 18.4R2-S5, 18.4R3, 19.1R2-S2, 19.1R3, 19.2R1-S5, 19.2R2, 19.3R2-S3, 19.3R3, 19.4R1-S3, 19.4R2, 20.1R1, and all subsequent releases.

Workaround: There are no viable workarounds for this issue.

Exploitation: Juniper SIRT is not aware of any malicious exploitation of this vulnerability.

References (1)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2020-1645 badge
[![CVE-2020-1645](https://trackcve.app/badge/CVE-2020-1645.svg)](https://trackcve.app/cve/CVE-2020-1645)

Record last updated .