dbcve.org
JunosOperating system · Juniper

CVE-2022-22226

MEDIUM · 6.5 CVSS v3.1 Published 2022-10-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In VxLAN scenarios on EX4300-MP, EX4600, QFX5000 Series devices an Uncontrolled Memory Allocation vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS allows an unauthenticated adjacently located attacker sending specific packets to cause a Denial of Service (DoS) condition by crashing one or more PFE's when they are received and processed by the device. Upon automatic restart of the PFE, continued processing of these packets will cause the memory leak to reappear. Depending on the volume of packets received the attacker may be able to create a sustained Denial of Service (DoS) condition. This issue affects: Juniper Networks Junos OS on EX4300-MP, EX4600, QFX5000 Series: 17.1 version 17.1R1 and later versions prior to 17.3R3-S12; 17.4 versions prior to 17.4R2-S13, 17.4R3-S5; 18.1 versions prior to 18.1R3-S13; 18.2 versions prior to 18.2R3-S8; 18.3 versions prior to 18.3R3-S5; 18.4 versions prior to 18.4R1-S8, 18.4R2-S6, 18.4R3-S6; 19.1 versions prior to 19.1R3-S4; 19.2 versions prior to 19.2R1-S7, 19.2R3-S1; 19.3 versions prior to 19.3R2-S6, 19.3R3-S1; 19.4 versions prior to 19.4R1-S4, 19.4R2-S4, 19.4R3-S1; 20.1 versions prior to 20.1R2; 20.2 versions prior to 20.2R2-S3, 20.2R3; 20.3 versions prior to 20.3R2. This issue does not affect Junos OS versions prior to 17.1R1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An uncontrolled memory allocation vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS on EX4300-MP, EX4600, and QFX5000 Series devices allows an unauthenticated adjacent attacker to send specific VxLAN packets that cause PFE crashes and memory leaks, leading to sustained DoS conditions.

MitigationApply the relevant Junos OS software update from the fixed versions listed (17.4R2-S13, 17.4R3-S5, 18.1R3-S13, 18.2R3-S8, 18.3R3-S5, 18.4R3-S6, 19.1R3-S4, 19.2R3-S1, 19.3R3-S1, 19.4R3-S1, 20.1R2, 20.2R3, or 20.3R2 depending on the release train in use).

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JunosOperating system
Affected:= 17.1= 17.2= 17.2x75= 17.3= 17.4= 18.1= 18.2= 18.3= 18.4= 19.1= 19.2= 19.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Run 'show chassis hardware' or 'show system information' to confirm the device is an EX4300-MP, EX4600, or QFX5000 Series switch
    Affected if Device model is EX4300-MP, EX4600, or QFX5000 Series
  2. Check Junos OS version
    Run 'show version' and compare the installed Junos version against the affected versions: 17.1, 17.2, 17.2x75, 17.3, 17.4, 18.1, 18.2, 18.3, 18.4, 19.1, 19.2, or 19.3
    Affected if Installed Junos version matches any of the listed affected versions
  3. Verify VxLAN feature is configured
    Run 'show configuration protocols vxlan' or 'show configuration vlans' to check for VxLAN-related configuration
    Affected if VxLAN protocol is enabled or VLANs are configured with VxLAN settings

A user is affected if the device is an EX4300-MP, EX4600, or QFX5000 Series switch running an affected Junos version with VxLAN configured and accessible to adjacent attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant Junos OS software update from the fixed versions listed (17.4R2-S13, 17.4R3-S5, 18.1R3-S13, 18.2R3-S8, 18.3R3-S5, 18.4R3-S6, 19.1R3-S4, 19.2R3-S1, 19.3R3-S1, 19.4R3-S1, 20.1R2, 20.2R3, or 20.3R2 depending on the release train in use).

Recommended fix High confidence

Upgrade to one of the fixed releases: 17.3R3-S12, 17.4R2-S13, 17.4R3-S5, 18.1R3-S13, 18.2R3-S8, 18.3R3-S5, 18.4R1-S8, 18.4R2-S6, 18.4R3-S6, 19.1R3-S4, 19.2R1-S7, 19.2R3-S1, 19.3R2-S6, 19.3R3-S1, 19.4R1-S4, 19.4R2-S4, 19.4R3-S1, 20.1R2, 20.2R2-S3, 20.2R3, or 20.3R2 (depending on your version branch)

  1. 1. Identify the current Junos OS version on the affected EX4300-MP, EX4600, or QFX5000 Series device using 'show version'
  2. 2. Determine the appropriate upgrade path based on the current version branch (17.1, 17.2, 17.3, 17.4, 18.x, 19.x, or 20.x)
  3. 3. Download the corresponding fixed Junos OS release from the Juniper Networks support portal
  4. 4. Upload the new Junos OS image to the device using 'request system software add <package>' or through the Web UI
  5. 5. Reboot the device to apply the new software using 'request system reboot'
  6. 6. After reboot, verify the new version is running with 'show version' and confirm the fix is applied
  7. 7. If using VxLAN, verify normal operation and monitor for any PFE crashes
Caveat Standard Junos upgrade considerations apply - review release notes for any changes to features or configuration commands used in your environment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Junos Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22226 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-22226 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data