dbcve.org
JunosOperating system · Juniper

CVE-2022-22210

MEDIUM · 6.5 CVSS v3.1 Published 2022-07-20
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
A NULL Pointer Dereference vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS on QFX5000 Series and MX Series allows an unauthenticated adjacent attacker to cause a Denial of Service (DoS). On QFX5K Series and MX Series, when the PFE receives a specific VxLAN packet the Layer 2 Address Learning Manager (L2ALM) process will crash leading to an FPC reboot. Continued receipt of this specific packet will create a sustained Denial of Service (DoS) condition. This issue affects Juniper Networks Junos OS on QFX5000 Series, MX Series: 20.3 versions prior to 20.3R3-S3; 20.4 versions prior to 20.4R3-S2; 21.2 versions prior to 21.2R2-S1. This issue does not affect Juniper Networks Junos OS: All versions prior to 20.3R1; 21.1 version 21.1R1 and later versions.

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

A NULL Pointer Dereference in the Packet Forwarding Engine causes the L2ALM process to crash when receiving a specific VxLAN packet on QFX5000 and MX Series devices, resulting in FPC reboot and sustained DoS. The vulnerability is triggerable by adjacent unauthenticated attackers sending malformed VxLAN traffic.

MitigationUpgrade Junos OS to 20.3R3-S3, 20.4R3-S2, or 21.2R2-S1 or later. Until upgrade, consider network segmentation to limit adjacent attack surface and implement VxLAN traffic filtering at perimeter devices.

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:= 20.3= 20.4= 21.2

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. Confirm device model is QFX5000 or MX Series
    Run 'show chassis hardware' or 'show version' to identify the device model
    Affected if Device is a QFX5000 series switch or MX Series router
  2. Check installed Junos version
    Run 'show version' and examine the Junos OS version number
    Affected if Version is exactly 20.3, 20.4, or 21.2 (base releases before S补丁)
  3. Verify if VxLAN is configured
    Run 'show configuration protocols vxlan' or search for 'vxlan' in configuration with 'show configuration | match vxlan'
    Affected if VxLAN protocol is actively configured on the device
  4. Check network exposure to adjacent attackers
    Review interface configurations and access control lists to determine if untrusted network segments can send traffic to the device's VxLAN-facing interfaces
    Affected if Device is accessible from untrusted adjacent network segments without VxLAN traffic filtering

A user is affected if they have a QFX5000 or MX Series device running Junos 20.3, 20.4, or 21.2 with VxLAN enabled and exposed to adjacent network attackers who can send malformed VxLAN packets.

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

Upgrade Junos OS to 20.3R3-S3, 20.4R3-S2, or 21.2R2-S1 or later. Until upgrade, consider network segmentation to limit adjacent attack surface and implement VxLAN traffic filtering at perimeter devices.

Recommended fix High confidence

20.3R3-S3 or later (for 20.3.x); 20.4R3-S2 or later (for 20.4.x); 21.2R2-S1 or later (for 21.2.x)

  1. 1. Identify the current Junos OS version running on the affected QFX5000 Series or MX Series device using the command: show version
  2. 2. Based on the current version, determine the minimum fixed release to upgrade to: For 20.3.x upgrade to 20.3R3-S3 or later; For 20.4.x upgrade to 20.4R3-S2 or later; For 21.2.x upgrade to 21.2R2-S1 or later
  3. 3. Plan maintenance window as upgrade will require device reboot
  4. 4. Download the appropriate Junos OS upgrade image from the Juniper Networks download portal (https://www.juniper.net/customers/csc/software/)
  5. 5. Upload the upgrade image to the device using file transfer (SCP or FTP)
  6. 6. Verify the image integrity using the command: request system software validate <image pathname>
  7. 7. Install the upgrade using: request system software add <image pathname> reboot
  8. 8. After reboot, verify the new version is running: show version
Caveat Standard Junos upgrade - requires maintenance window and FPC reboot; ensure proper configuration backup before upgrade

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

Fix this in Junos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22210 — 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-22210 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