LiveActive security incident?Get immediate response
CVE Record

CVE-2020-1638: Junos OS & Junos OS Evolved: A specific IPv4 packet can lead to FPC restart.

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.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A crafted IPv4 packet sent to certain Juniper routing and switching platforms can restart line-card hardware. When that FPC restarts, traffic through it drops; repeated packets can create a sustained outage. Risk is highest for exposed control planes on affected MX, PTX, and QFX platforms running the cited Junos 19.2-19.4 or Junos OS Evolved releases.

Executive priority

Treat this as high priority for core network infrastructure because successful exploitation can interrupt traffic forwarding. It is not described as data theft or system takeover, but outage impact can be material where affected FPCs carry production traffic.

Technical view

CVE-2020-1638 is a network unauthenticated denial-of-service issue in specific Junos OS and Junos OS Evolved releases. The packet must be IPv4 and destined to the device itself, reaching the Routing Engine despite edge and control-plane filters. IPv6 is not affected. Affected hardware includes MX with MPC10E/MPC11E, PTX10001, QFX5220, and PTX10003 series.

Likely exposure

Exposure is limited to listed Juniper platforms and software versions. Devices with reachable management, control-plane, or device-destined IPv4 paths have higher concern. Existing edge and control-plane filtering may reduce reachability, but the source does not say filtering fully mitigates the issue.

Exploitation context

The provided sources do not report active exploitation, and the CVE is not marked KEV. The vulnerability is remotely reachable with low attack complexity and no privileges, but only when the specific IPv4 traffic reaches the device itself. Repeated triggering can extend denial of service.

Researcher notes

The key exposure boundary is device-destined IPv4 reaching the Routing Engine, not transit IPv4 or IPv6 generally. Sources identify affected trains and platforms but provide limited mitigation detail beyond fixed releases and existing filtering context. Do not assume all Junos devices are affected.

Mitigation direction

  • Upgrade Junos OS 19.2, 19.3, or 19.4 to the fixed releases named by Juniper.
  • For Junos OS Evolved, follow Juniper advisory guidance for fixed or unaffected releases.
  • Restrict device-destined IPv4 traffic through edge and control-plane filters.
  • Prioritize internet-facing or provider-edge devices carrying critical traffic.
  • Monitor for unexpected FPC restarts and traffic drops until remediation is complete.

Validation and detection

  • Inventory affected MX, PTX, and QFX platforms and installed Junos releases.
  • Confirm whether MPC10E, MPC11E, PTX10001, QFX5220, or PTX10003 hardware is present.
  • Check whether IPv4 traffic can reach the device control plane from untrusted networks.
  • Review logs and telemetry for FPC restarts or correlated traffic drops.
  • Verify installed versions meet or exceed Juniper's named fixed releases.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-467: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-1638 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2020-1638Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Juniper NetworksJunos OS19.2, 19.3, 19.4Listed
Juniper NetworksJunos OSunspecifiedListed
Juniper NetworksJunos OS Evolved19.2-EVO, 19.3-EVO 19.2-EVO, 19.4-EVOListed
Juniper NetworksJunos OS EvolvedunspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-467 · source CWE mapping

Use of sizeof() on a Pointer Type

Use of sizeof() on a Pointer Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.