title: Junos OS: MX Series: Services card might restart when DNS filtering is enabled
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.
problem types: CWE-362 Race Condition (Concurrent Execution using Shared Resource with Improper Synchronization)
affected:
{
platforms: MX Series
product: Junos OS
vendor: Juniper Networks
versions:
lessThan: 17.3R2, status: unaffected, version: unspecified, versionType: custom
status: unaffected, version: 17.4
status: unaffected, version: 18.1
status: unaffected, version: 18.2
lessThan: 17.3R3-S8, status: affected, version: 17.3, versionType: custom
lessThan: 18.3R2-S4, 18.3R3-S1, status: affected, version: 18.3, versionType: custom
lessThan: 18.4R2-S5, 18.4R3, status: affected, version: 18.4, versionType: custom
lessThan: 19.1R2-S2, 19.1R3, status: affected, version: 19.1, versionType: custom
lessThan: 19.2R1-S5, 19.2R2, status: affected, version: 19.2, versionType: custom
lessThan: 19.3R2-S3, 19.3R3, status: affected, version: 19.3, versionType: custom
lessThan: 19.4R1-S3, 19.4R2, status: affected, version: 19.4, versionType: custom
}
metrics:
cvssV3_1: [
attackComplexity: LOW
attackVector: NETWORK
availabilityImpact: LOW
baseScore: 8.3
baseSeverity: HIGH
confidentialityImpact: LOW
integrityImpact: LOW
privilegesRequired: NONE
scope: CHANGED
userInteraction: NONE
vectorString: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L
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: 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.
workarounds: There are no viable workarounds for this issue.