LiveActive security incident?Get immediate response
CVE Record

CVE-2022-22217: Junos OS: QFX10K Series: Denial of Service (DoS) upon receipt of crafted MLD packets on multi-homing ESI in VXLAN

An Improper Check for Unusual or Exceptional Conditions vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS allows an adjacent unauthenticated attacker to cause a Denial of Service (DoS). The issue is caused by malformed MLD packets looping on a multi-homed Ethernet Segment Identifier (ESI) when VXLAN is configured. These MLD packets received on a multi-homed ESI are sent to the peer, and then incorrectly forwarded out the same ESI, violating the split horizon rule. This issue only affects QFX10K Series switches, including the QFX10002, QFX10008, and QFX10016. Other products and platforms are unaffected by this vulnerability. This issue affects Juniper Networks Junos OS on QFX10K Series: All versions prior to 19.1R3-S9; 19.2 versions prior to 19.2R1-S9, 19.2R3-S5; 19.3 versions prior to 19.3R3-S6; 19.4 versions prior to 19.4R2-S7, 19.4R3-S8; 20.1 versions prior to 20.1R3-S4; 20.2 versions prior to 20.2R3-S4; 20.3 versions prior to 20.3R3-S2; 20.4 versions prior to 20.4R3-S2; 21.1 versions prior to 21.1R3; 21.2 versions prior to 21.2R2-S1, 21.2R3; 21.3 versions prior to 21.3R2.

MediumCVSS 6.1Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This vulnerability can let a nearby, unauthenticated attacker disrupt specific Juniper QFX10K switches when VXLAN and multi-homed ESI are in use. The issue can cause denial of service by mishandling malformed MLD traffic. It is not described as internet-routable or broadly affecting all Juniper platforms.

Executive priority

Treat as a targeted network availability risk for QFX10K data center environments. It should be prioritized where VXLAN multi-homing supports critical services, but it is not described as broad remote compromise or active exploitation in the provided sources.

Technical view

CVE-2022-22217 is a Junos OS PFE improper exceptional-condition check. Malformed MLD packets on a multi-homed ESI in VXLAN can loop between peers and be forwarded out the same ESI, violating split horizon behavior. Affected platforms are QFX10K Series, including QFX10002, QFX10008, and QFX10016.

Likely exposure

Exposure is limited to affected Junos OS versions on QFX10K Series switches using VXLAN with multi-homed ESI. Other Juniper products and platforms are stated as unaffected. The attacker must be adjacent, which narrows practical reach but matters in shared, campus, data center, or tenant-adjacent networks.

Exploitation context

The source bundle does not indicate known active exploitation, and KEV is false. The attack is adjacent, unauthenticated, and low complexity, but the described outcome is denial of service with limited integrity and availability impact rather than remote system compromise.

Researcher notes

Key scoping factors are platform, Junos OS train, VXLAN, and multi-homed ESI. The reported flaw is forwarding logic around malformed MLD handling and split horizon enforcement. Evidence is sufficient for affected-version triage, but exploit prevalence and workaround details are not provided in the bundle.

Mitigation direction

  • Upgrade affected QFX10K switches to a fixed Junos OS release listed by Juniper.
  • Review Juniper JSA69721 for exact release guidance and supported operational mitigations.
  • Prioritize VXLAN environments using multi-homed ESI on QFX10002, QFX10008, or QFX10016.
  • Limit untrusted adjacent access to vulnerable network segments where feasible.
  • Plan maintenance carefully because remediation may require network switch upgrades.

Validation and detection

  • Inventory QFX10002, QFX10008, and QFX10016 devices and record Junos OS versions.
  • Confirm whether VXLAN and multi-homed ESI are configured on each device.
  • Compare installed versions against Juniper's affected and fixed release thresholds.
  • Review monitoring for unexplained PFE, forwarding, or DoS-like instability.
  • Document unaffected platforms separately to avoid unnecessary remediation scope.
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-754: 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-2022-22217 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
Medium
CVSS
6.1 (3.1)
Known Exploited
No
Published

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

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
6.1CVSS 3.1MediumCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:L2.82.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.1Medium
CVSS 3.1 vector shape for CVE-2022-22217Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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 OSunspecified, 19.2, 19.3, 19.4, 20.1, 20.2, 20.3, 20.4, 21.1, 21.2, 21.3Listed
Weakness

CWE details

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

CWE-754 · source CWE mapping

Improper Check for Unusual or Exceptional Conditions

Improper Check for Unusual or Exceptional Conditions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.