LiveActive security incident?Get immediate response
CVE Record

CVE-2022-22203: Junos OS: EX4600 Series and QFX5000 Series: Receipt of specific traffic will lead to an fxpc process crash followed by an FPC reboot

An Incorrect Comparison vulnerability in PFE of Juniper Networks Junos OS allows an adjacent unauthenticated attacker to cause a Denial of Service (DoS). On QFX5000 Series, and EX4600 and EX4650 platforms, the fxpc process will crash followed by the FPC reboot upon receipt of a specific hostbound packet. Continued receipt of these specific packets will create a sustained Denial of Service (DoS) condition. This issue only affects Juniper Networks Junos OS 19.4 version 19.4R3-S4.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This flaw can make certain Juniper switching platforms reboot part of their forwarding hardware after receiving specific nearby network traffic. The main business impact is availability: repeated traffic could keep affected devices unstable and disrupt connected services. The source bundle limits the affected Junos OS release to 19.4R3-S4.

Executive priority

Treat as a moderate availability risk for affected Juniper switching infrastructure. Prioritize validation because the affected version scope is narrow, but business impact can be material if critical switching paths repeatedly reboot.

Technical view

CVE-2022-22203 is a CWE-697 incorrect comparison issue in Junos OS PFE. On QFX5000 Series, EX4600, and EX4650 platforms running Junos OS 19.4R3-S4, an adjacent unauthenticated attacker can trigger an fxpc crash followed by FPC reboot via specific hostbound traffic, causing DoS if repeated.

Likely exposure

Exposure appears limited to affected Juniper QFX5000 Series, EX4600, and EX4650 devices running Junos OS 19.4R3-S4 where an adjacent attacker can send the relevant hostbound traffic. The bundle does not identify other affected releases.

Exploitation context

The CVSS vector requires adjacent network access, low complexity, no privileges, and no user interaction. The issue affects availability only. The source bundle says KEV is false and provides no cited evidence of active exploitation.

Researcher notes

Do not broaden scope beyond the cited platforms and Junos OS 19.4R3-S4. The bundle does not provide packet details, fixed versions, workarounds, or exploitation evidence. Use Juniper JSA69707 as the authority for remediation specifics.

Mitigation direction

  • Identify Juniper QFX5000, EX4600, and EX4650 assets.
  • Check whether any run Junos OS 19.4R3-S4.
  • Review Juniper advisory JSA69707 for supported remediation.
  • Prioritize vendor-guided remediation for exposed or critical switching paths.
  • Monitor for repeated fxpc crashes and FPC reboots.

Validation and detection

  • Inventory platform model and Junos OS release for each Juniper switch.
  • Confirm whether the exact affected release is 19.4R3-S4.
  • Review operational logs for fxpc process crashes.
  • Review device history for FPC reboot patterns.
  • Assess whether untrusted adjacent networks can reach hostbound traffic paths.
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-697: 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-22203 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.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/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
6.5CVSS 3.1MediumCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:A/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 OSunspecified, 19.4Listed
Weakness

CWE details

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

CWE-697 · source CWE mapping

Incorrect Comparison

Incorrect Comparison represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.