dbcve.org
JunosOperating system · Juniper

CVE-2022-22171

HIGH · 7.5 CVSS v3.1 Published 2022-01-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable 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
An Improper Check for Unusual or Exceptional Conditions vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS allows an unauthenticated networked attacker to cause a Denial of Service (DoS) by sending specific packets over VXLAN which cause the PFE to reset. This issue affects: Juniper Networks Junos OS 19.4 versions prior to 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-S1; 21.1 versions prior to 21.1R3; 21.2 versions prior to 21.2R2; 21.3 versions prior to 21.3R1-S1, 21.3R2. This issue does not affect versions of Junos OS prior to 19.4R1.

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 improper check for unusual or exceptional conditions in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS allows an unauthenticated network attacker to cause denial of service by sending specific packets over VXLAN that trigger a PFE reset.

MitigationUpgrade Junos OS to the patched versions specified (19.4R3-S7, 20.1R3-S3, 20.2R3-S3, 20.3R3-S2, 20.4R3-S1, 21.1R3, 21.2R2, or 21.3R2+) to remediate this vulnerability.

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:= 19.4= 20.1= 20.2= 20.3= 20.4= 21.1= 21.2= 21.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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/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. Check Junos OS version
    Run 'show version' command on the device and note the installed Junos version
    Affected if The installed version matches 19.4, 20.1, 20.2, 20.3, 20.4, 21.1, 21.2, or 21.3 (any release within these version lines)
  2. Verify VXLAN configuration
    Run 'show configuration | display set | match vxlan' to see if VXLAN features or tunnels are configured
    Affected if VXLAN is configured and active on the device
  3. Check for VXLAN-enabled interfaces
    Run 'show interfaces vxlan' to list all VXLAN tunnel interfaces and their status
    Affected if Any VXLAN tunnel interfaces are in 'up' state
  4. Identify VXLAN routing instances
    Run 'show configuration routing-instances | display set | match vxlan' to find VXLAN-based routing instances
    Affected if VXLAN routing instances are configured with VXLAN encapsulation

The device is affected if it runs any of the listed vulnerable Junos versions AND has VXLAN functionality configured or enabled, as the vulnerability is triggered by specific 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 the patched versions specified (19.4R3-S7, 20.1R3-S3, 20.2R3-S3, 20.3R3-S2, 20.4R3-S1, 21.1R3, 21.2R2, or 21.3R2+) to remediate this vulnerability.

Recommended fix High confidence

Upgrade to 19.4R3-S7 (for 19.4 branch), 20.1R3-S3 (for 20.1 branch), 20.2R3-S3 (for 20.2 branch), or 20.3R3-S2 (for 20.3 branch)

  1. 1. Identify the current Junos OS version running on the device using 'show version'
  2. 2. Determine which affected branch (19.4, 20.1, 20.2, or 20.3) the current version belongs to
  3. 3. Download the appropriate fixed version from Juniper Networks: for 19.4 branch upgrade to 19.4R3-S7, for 20.1 branch upgrade to 20.1R3-S3, for 20.2 branch upgrade to 20.2R3-S3, for 20.3 branch upgrade to 20.3R3-S2
  4. 4. Upload the Junos OS upgrade package to the device
  5. 5. Initiate the upgrade using 'request system software add <package>' with the appropriate options (e.g., no-validate, reboot)
  6. 6. After upgrade completes, verify the new version is running with 'show version'
  7. 7. Confirm VXLAN functionality is operational and PFE is stable
Caveat Standard Junos OS upgrade considerations apply - review Juniper release notes for any behavior changes between versions

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

Fix this in Junos Scoped from the published advisory
  • Consultation8.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,660
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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