CVE-2022-22202

Junos OS: PTX Series: FPCs may restart unexpectedly upon receipt of specific MPLS packets with certain multi-unit interface configurations

MEDIUM
6.5
CVSS Score
Published: July 20, 2022 at 02:10 PM UTC
Updated: June 17, 2026 at 04:27 AM UTC
7 products affected across 2 vendorsJunosPtx10008Ptx10016

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
MEDIUM6.5
Exploit prediction
EPSS 0.5%

Description

An Improper Handling of Exceptional Conditions vulnerability on specific PTX Series devices, including the PTX1000, PTX3000 (NextGen), PTX5000, PTX10002-60C, PTX10008, and PTX10016 Series, in Juniper Networks Junos OS allows an unauthenticated MPLS-based attacker to cause a Denial of Service (DoS) by triggering the dcpfe process to crash and FPC to restart. On affected PTX Series devices, processing specific MPLS packets received on an interface with multiple units configured may cause FPC to restart unexpectedly. Continued receipt and processing of this packet will create a sustained Denial of Service (DoS) condition. This issue only affects PTX Series devices utilizing specific FPCs found on PTX1000, PTX3000 (NextGen), PTX5000, PTX10002-60C, PTX10008, and PTX10016 Series devices, only if multiple units are configured on the ingress interface, and at least one unit has 'family mpls' *not* configured. See the configuration sample below for more information. No other platforms are affected by this vulnerability. This issue affects: Juniper Networks Junos OS on PTX Series: All versions prior to 19.1R3-S9; 19.2 versions prior to 19.2R3-S6; 19.3 versions prior to 19.3R3-S6; 19.4 versions prior to 19.4R3-S8; 20.1 versions prior to 20.1R3-S4; 20.2 versions prior to 20.2R3-S5; 20.3 versions prior to 20.3R3-S4; 20.4 versions prior to 20.4R3-S4; 21.1 versions prior to 21.1R3-S2; 21.2 versions prior to 21.2R3-S1; 21.3 versions prior to 21.3R3; 21.4 versions prior to 21.4R2; 22.1 versions prior to 22.1R2.

Affected

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

v < 19.1v < 19.1R3-S919.2 ≤ v < 19.2R3-S619.3 ≤ v < 19.3R3-S619.4 ≤ v < 19.4R3-S820.1 ≤ v < 20.1R3-S420.2 ≤ v < 20.2R3-S520.3 ≤ v < 20.3R3-S420.4 ≤ v < 20.4R3-S421.1 ≤ v < 21.1R3-S221.2 ≤ v < 21.2R3-S121.3 ≤ v < 21.3R321.4 ≤ v < 21.4R222.1 ≤ v < 22.1R219.119.1 r119.1 r1-s119.1 r1-s219.1 r1-s319.1 r1-s419.1 r1-s519.1 r1-s619.1 r219.1 r2-s119.1 r2-s219.1 r2-s319.1 r319.1 r3-s119.1 r3-s219.1 r3-s319.1 r3-s419.1 r3-s519.1 r3-s619.1 r3-s719.1 r3-s819.219.2 r119.2 r1-s119.2 r1-s219.2 r1-s319.2 r1-s419.2 r1-s519.2 r1-s619.2 r1-s719.2 r1-s819.2 r1-s919.2 r219.2 r2-s119.2 r319.2 r3-s119.2 r3-s219.2 r3-s319.2 r3-s419.2 r3-s519.319.3 r119.3 r1-s119.3 r219.3 r2-s119.3 r2-s219.3 r2-s319.3 r2-s419.3 r2-s519.3 r2-s619.3 r319.3 r3-s119.3 r3-s219.3 r3-s319.3 r3-s419.3 r3-s519.419.4 r119.4 r1-s119.4 r1-s219.4 r1-s319.4 r1-s419.4 r219.4 r2-s119.4 r2-s219.4 r2-s319.4 r2-s419.4 r2-s519.4 r2-s619.4 r319.4 r3-s119.4 r3-s219.4 r3-s319.4 r3-s419.4 r3-s519.4 r3-s619.4 r3-s720.120.1 r120.1 r1-s120.1 r1-s220.1 r1-s320.1 r1-s420.1 r220.1 r2-s120.1 r2-s220.1 r320.1 r3-s120.1 r3-s220.1 r3-s320.220.2 r120.2 r1-s120.2 r1-s220.2 r1-s320.2 r220.2 r2-s120.2 r2-s220.2 r2-s320.2 r320.2 r3-s120.2 r3-s220.2 r3-s320.2 r3-s420.320.3 r120.3 r1-s120.3 r1-s220.3 r220.3 r2-s120.3 r320.3 r3-s120.3 r3-s220.3 r3-s320.420.4 r120.4 r1-s120.4 r220.4 r2-s120.4 r2-s220.4 r320.4 r3-s120.4 r3-s221.121.1 r121.1 r1-s121.1 r221.1 r2-s121.1 r2-s221.1 r321.1 r3-s121.221.2 r121.2 r1-s121.2 r1-s221.2 r221.2 r2-s121.2 r2-s221.2 r321.321.3 r121.3 r1-s121.3 r1-s221.3 r221.3 r2-s121.3 r2-s221.421.4 r121.4 r1-s121.4 r1-s222.122.1 r1
Affected range stops below 19.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.1R3-S9, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.2R3-S6, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.3R3-S6, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.4R3-S8, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.1R3-S4, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.2R3-S5, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.3R3-S4, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.4R3-S4, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.1R3-S2, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.2R3-S1, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.3R3, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.4R2, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.1R2, so it looks safe — our inference, not a vendor statement
juniper-ptx1000 (environment) · juniper-ptx10002-60c (environment) · juniper-ptx10008 (environment) · juniper-ptx10016 (environment) · juniper-ptx3000 (environment) · juniper-ptx5000 (environment)
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_CONFIRMExploitMitigationVendor Advisory
https://kb.juniper.net/JSA69706

CVSS

6.5MEDIUMjuniper
Attack Vector
ADJACENT_NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-755

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