CVE-2020-1638

Junos OS & Junos OS Evolved: A specific IPv4 packet can lead to FPC restart.

HIGH
7.5
CVSS Score
Published: April 8, 2020 at 07:26 PM UTC
Updated: June 17, 2026 at 03:02 AM UTC
12 products affected across 2 vendorsJunosJunos OS EvolvedMx960

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
HIGH7.5
Exploit prediction
EPSS 1%

Description

The FPC (Flexible PIC Concentrator) of Juniper Networks Junos OS and Junos OS Evolved may restart after processing a specific IPv4 packet. Only packets destined to the device itself, successfully reaching the RE through existing edge and control plane filtering, will be able to cause the FPC restart. When this issue occurs, all traffic via the FPC will be dropped. By continuously sending this specific IPv4 packet, an attacker can repeatedly crash the FPC, causing an extended Denial of Service (DoS) condition. This issue can only occur when processing a specific IPv4 packet. IPv6 packets cannot trigger this issue. This issue affects: Juniper Networks Junos OS on MX Series with MPC10E or MPC11E and PTX10001: 19.2 versions prior to 19.2R1-S4, 19.2R2; 19.3 versions prior to 19.3R2-S2, 19.3R3; 19.4 versions prior to 19.4R1-S1, 19.4R2. Juniper Networks Junos OS Evolved on on QFX5220, and PTX10003 series: 19.2-EVO versions; 19.3-EVO versions; 19.4-EVO versions prior to 19.4R2-EVO. This issue does not affect Junos OS versions prior to 19.2R1. This issue does not affect Junos OS Evolved versions prior to 19.2R1-EVO.

Affected

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

juniper-ptx10003 (environment) · juniper-qfx5220 (environment)
19.2 ≤ v < 19.2R1-S4, 19.2R219.3 ≤ v < 19.3R2-S2, 19.3R319.4 ≤ v < 19.4R1-S1, 19.4R219.219.2 r119.2 r1-s119.2 r1-s219.2 r1-s319.319.3 r119.3 r1-s119.3 r219.3 r2-s119.419.4 r1
Vendor states this is fixed in 19.2R1 (unaffected)
Affected range stops below 19.2R1-S4, 19.2R2, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.3R2-S2, 19.3R3, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.4R1-S1, 19.4R2, so it looks safe — our inference, not a vendor statement
juniper-mx10003 (environment) · juniper-mx2008 (environment) · juniper-mx2010 (environment) · juniper-mx2020 (environment) · juniper-mx240 (environment) · juniper-mx480 (environment) · juniper-mx960 (environment)
19.4-EVO ≤ v < 19.4R2-EVO19.2-EVO19.3-EVO 19.2-EVO19.4-EVO
Vendor states this is fixed in 19.2R1-EVO (unaffected)
Affected range stops below 19.4R2-EVO, so it looks safe — our inference, not a vendor statement
All versions
All versions
All versions
All versions
All versions
All versions
All versions

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/JSA11019

CVSS

7.5HIGHjuniper
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-467NVD-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