CVE-2022-22223

Junos OS: QFX10000 Series: In IP/MPLS PHP node scenarios upon receipt of certain crafted packets multiple interfaces in LAG configurations may detach.

HIGH

7.5

CVSS Score

Published: October 18, 2022 at 02:46 AM UTC

Updated: June 17, 2026 at 04:28 AM UTC

4 products affected across 2 vendorsJunosQfx10008Qfx10016

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

Start Free Sign In

Severity

HIGH7.5

Exploit prediction

EPSS 0.9%

SSVC

No known exploit

Description

On QFX10000 Series devices using Juniper Networks Junos OS when configured as transit IP/MPLS penultimate hop popping (PHP) nodes with link aggregation group (LAG) interfaces, an Improper Validation of Specified Index, Position, or Offset in Input weakness allows an attacker sending certain IP packets to cause multiple interfaces in the LAG to detach causing a Denial of Service (DoS) condition. Continued receipt and processing of these packets will sustain the Denial of Service. This issue affects IPv4 and IPv6 packets. Packets of either type can cause and sustain the DoS event. These packets can be destined to the device or be transit packets. On devices such as the QFX10008 with line cards, line cards can be restarted to restore service. On devices such as the QFX10002 you can restart the PFE service, or reboot device to restore service. This issue affects: Juniper Networks Junos OS on QFX10000 Series: All versions prior to 15.1R7-S11; 18.4 versions prior to 18.4R2-S10, 18.4R3-S10; 19.1 versions prior to 19.1R3-S8; 19.2 versions prior to 19.2R3-S4; 19.3 versions prior to 19.3R3-S5; 19.4 versions prior to 19.4R2-S6, 19.4R3-S7; 20.1 versions prior to 20.1R3-S3; 20.2 versions prior to 20.2R3-S3; 20.3 versions prior to 20.3R3-S2; 20.4 versions prior to 20.4R3-S4; 21.1 versions prior to 21.1R3; 21.2 versions prior to 21.2R3-S3; 21.3 versions prior to 21.3R3-S1. An indicator of compromise may be seen by issuing the command: request pfe execute target fpc0 command "show jspec pechip[3] registers ps l2_node 10" timeout 0 | refresh 1 | no-more and reviewing for backpressured output; for example: GOT: 0x220702a8 pe.ps.l2_node[10].pkt_cnt 00000076 GOT: 0x220702b4 pe.ps.l2_node[10].backpressured 00000002 <<<< STICKS HERE and requesting detail on the pepic wanio: request pfe execute target fpc0 command "show pepic 0 wanio-info" timeout 0 | no-more | match xe-0/0/0:2 GOT: 3 xe-0/0/0:2 10 6 3 0 1 10 189 10 0x6321b088 <<< LOOK HERE as well as looking for tail drops looking at the interface queue, for example: show interfaces queue xe-0/0/0:2 resulting in: Transmitted: Total-dropped packets: 1094137 0 pps << LOOK HERE

Affected

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

Junos · Juniper Networks

95%

v < 15.1v < 15.1R7-S1118.4 ≤ v < 18.4R2-S10, 18.4R3-S1019.1 ≤ v < 19.1R3-S819.2 ≤ v < 19.2R3-S419.3 ≤ v < 19.3R3-S519.4 ≤ v < 19.4R2-S6, 19.4R3-S720.1 ≤ v < 20.1R3-S320.2 ≤ v < 20.2R3-S320.3 ≤ v < 20.3R3-S220.4 ≤ v < 20.4R3-S421.1 ≤ v < 21.1R321.2 ≤ v < 21.2R3-S321.3 ≤ v < 21.3R3-S115.1 15.1 a1 15.1 f 15.1 f1 15.1 f2 15.1 f2-s1 15.1 f2-s2 15.1 f2-s3 15.1 f2-s4 15.1 f3 15.1 f4 15.1 f5 15.1 f5-s7 15.1 f6 15.1 f6-s1 15.1 f6-s10 15.1 f6-s12 15.1 f6-s2 15.1 f6-s3 15.1 f6-s4 15.1 f6-s5 15.1 f6-s6 15.1 f6-s7 15.1 f6-s8 15.1 f6-s9 15.1 f7 15.1 r 15.1 r1 15.1 r2 15.1 r3 15.1 r4 15.1 r4-s7 15.1 r4-s8 15.1 r4-s9 15.1 r5 15.1 r5-s1 15.1 r5-s3 15.1 r5-s5 15.1 r5-s6 15.1 r6 15.1 r6-s1 15.1 r6-s2 15.1 r6-s3 15.1 r6-s4 15.1 r6-s6 15.1 r7 15.1 r7-s1 15.1 r7-s10 15.1 r7-s2 15.1 r7-s3 15.1 r7-s4 15.1 r7-s5 15.1 r7-s6 15.1 r7-s7 15.1 r7-s8 15.1 r7-s9 18.4 18.4 r1 18.4 r1-s1 18.4 r1-s2 18.4 r1-s3 18.4 r1-s4 18.4 r1-s5 18.4 r1-s6 18.4 r1-s7 18.4 r2 18.4 r2-s1 18.4 r2-s2 18.4 r2-s3 18.4 r2-s4 18.4 r2-s5 18.4 r2-s6 18.4 r2-s7 18.4 r2-s8 18.4 r2-s9 18.4 r3 18.4 r3-s1 18.4 r3-s2 18.4 r3-s3 18.4 r3-s4 18.4 r3-s5 18.4 r3-s6 18.4 r3-s7 18.4 r3-s8 18.4 r3-s9 19.1 19.1 r1 19.1 r1-s1 19.1 r1-s2 19.1 r1-s3 19.1 r1-s4 19.1 r1-s5 19.1 r1-s6 19.1 r2 19.1 r2-s1 19.1 r2-s2 19.1 r2-s3 19.1 r3 19.1 r3-s1 19.1 r3-s2 19.1 r3-s3 19.1 r3-s4 19.1 r3-s5 19.1 r3-s6 19.1 r3-s7 19.2 19.2 r1 19.2 r1-s1 19.2 r1-s2 19.2 r1-s3 19.2 r1-s4 19.2 r1-s5 19.2 r1-s6 19.2 r1-s7 19.2 r1-s8 19.2 r1-s9 19.2 r2 19.2 r2-s1 19.2 r3 19.2 r3-s1 19.2 r3-s2 19.2 r3-s3 19.3 19.3 r1 19.3 r1-s1 19.3 r2 19.3 r2-s1 19.3 r2-s2 19.3 r2-s3 19.3 r2-s4 19.3 r2-s5 19.3 r2-s6 19.3 r3 19.3 r3-s1 19.3 r3-s2 19.3 r3-s3 19.3 r3-s4 19.4 19.4 r1 19.4 r1-s1 19.4 r1-s2 19.4 r1-s3 19.4 r1-s4 19.4 r2 19.4 r2-s1 19.4 r2-s2 19.4 r2-s3 19.4 r2-s4 19.4 r2-s5 19.4 r3 19.4 r3-s1 19.4 r3-s2 19.4 r3-s3 19.4 r3-s4 19.4 r3-s5 19.4 r3-s6 20.1 20.1 r1 20.1 r1-s1 20.1 r1-s2 20.1 r1-s3 20.1 r1-s4 20.1 r2 20.1 r2-s1 20.1 r2-s2 20.1 r3 20.1 r3-s1 20.1 r3-s2 20.2 20.2 r1 20.2 r1-s1 20.2 r1-s2 20.2 r1-s3 20.2 r2 20.2 r2-s1 20.2 r2-s2 20.2 r2-s3 20.2 r3 20.2 r3-s1 20.2 r3-s2 20.3 20.3 r1 20.3 r1-s1 20.3 r1-s2 20.3 r2 20.3 r2-s1 20.3 r3 20.3 r3-s1 20.4 20.4 r1 20.4 r1-s1 20.4 r2 20.4 r2-s1 20.4 r2-s2 20.4 r3 20.4 r3-s1 20.4 r3-s2 20.4 r3-s3 21.1 21.1 r1 21.1 r1-s1 21.1 r2 21.1 r2-s1 21.1 r2-s2 21.2 21.2 r1 21.2 r1-s1 21.2 r1-s2 21.2 r2 21.2 r2-s1 21.2 r2-s2 21.2 r3 21.2 r3-s2 21.3 21.3 r1 21.3 r1-s1 21.3 r1-s2 21.3 r2 21.3 r2-s1 21.3 r2-s2 21.3 r3

Affected range stops below 15.1, so it looks safe — our inference, not a vendor statement

Affected range stops below 15.1R7-S11, so it looks safe — our inference, not a vendor statement

Affected range stops below 18.4R2-S10, 18.4R3-S10, so it looks safe — our inference, not a vendor statement

Affected range stops below 19.1R3-S8, so it looks safe — our inference, not a vendor statement

Affected range stops below 19.2R3-S4, so it looks safe — our inference, not a vendor statement

Affected range stops below 19.3R3-S5, so it looks safe — our inference, not a vendor statement

Affected range stops below 19.4R2-S6, 19.4R3-S7, so it looks safe — our inference, not a vendor statement

Affected range stops below 20.1R3-S3, so it looks safe — our inference, not a vendor statement

Affected range stops below 20.2R3-S3, so it looks safe — our inference, not a vendor statement

Affected range stops below 20.3R3-S2, 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, so it looks safe — our inference, not a vendor statement

Affected range stops below 21.2R3-S3, so it looks safe — our inference, not a vendor statement

Affected range stops below 21.3R3-S1, so it looks safe — our inference, not a vendor statement

juniper-qfx10002 (environment) · juniper-qfx10008 (environment) · juniper-qfx10016 (environment)

Qfx10002 · Juniperdevice

80%

All versions

Qfx10008 · Juniperdevice

80%

All versions

Qfx10016 · Juniperdevice

80%

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

https://kb.juniper.net/JSA69873

References (1)

ExploitMitigationVendor Advisory

Source: [email protected]

https://kb.juniper.net/JSA69873

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGH[email protected]

Attack Vector: NETWORK
Complexity: LOW
Privileges: NONE
User Interaction: NONE
Scope: UNCHANGED
Confidentiality: NONE
Integrity: NONE
Availability: HIGH

Vector?

Quick Info

StatusMODIFIED

CWE

CWE-1285CWE-20

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.

Create account Sign in

Free plan, no card