dbcve.org
JunosOperating system · Juniper

CVE-2022-22214

MEDIUM · 6.5 CVSS v3.1 Published 2022-07-20
Fix available
A fix is available. Upgrade to 12.3 / 20.4 or later.
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
An Improper Input Validation vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS and Junos OS Evolved allows an adjacent attacker to cause a PFE crash and thereby a Denial of Service (DoS). An FPC will crash and reboot after receiving a specific transit IPv6 packet over MPLS. Continued receipt of this packet will create a sustained Denial of Service (DoS) condition. This issue does not affect systems configured for IPv4 only. This issue affects: Juniper Networks Junos OS All versions prior to 12.3R12-S21; 15.1 versions prior to 15.1R7-S10; 17.3 versions prior to 17.3R3-S12; 18.3 versions prior to 18.3R3-S6; 18.4 versions prior to 18.4R2-S9, 18.4R3-S9; 19.1 versions prior to 19.1R2-S3, 19.1R3-S7; 19.2 versions prior to 19.2R1-S7, 19.2R3-S3; 19.3 versions prior to 19.3R2-S7, 19.3R3-S4; 19.4 versions prior to 19.4R3-S5; 20.1 versions prior to 20.1R3; 20.2 versions prior to 20.2R3-S2; 20.3 versions prior to 20.3R3; 20.4 versions prior to 20.4R2-S2, 20.4R3; 21.1 versions prior to 21.1R2. Juniper Networks Junos OS Evolved All versions prior to 20.4R3-S3-EVO; 21.2 versions prior to 21.2R3-EVO; 21.3 versions prior to 21.3R2-S1-EVO, 21.3R3-EVO; 21.4 versions prior to 21.4R2-EVO.

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

Improper input validation in the Juniper Packet Forwarding Engine (PFE) allows an adjacent attacker to cause a denial of service by sending a specific transit IPv6 packet over MPLS. The malformed packet triggers an FPC crash and reboot, and continued receipt creates a sustained DoS condition. Only systems with IPv6 enabled are affected; IPv4-only configurations are not vulnerable.

MitigationApply the vendor-supplied patches for the specific Junos OS/Evolved version or, as a compensating control, disable IPv6 if not required and implement MPLS access controls to limit exposure to adjacent attackers.

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:< 12.3= 12.3= 12.3r12= 15.1= 17.3= 18.3= 18.4= 19.1= 19.2= 19.3= 19.4= 20.1
Junos Os EvolvedOperating system
Affected:< 20.4= 20.4= 21.2= 21.3= 21.4

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. Verify IPv6 is enabled on the device
    Check the device configuration for IPv6 protocol settings or interfaces configured with IPv6 addresses. On Junos, this can be verified by reviewing the active configuration for any 'family inet6' statements or IPv6 protocol configurations.
    Affected if IPv6 is enabled or configured on any interface - the device is only vulnerable when IPv6 is active; IPv4-only configurations are not affected by this CVE.
  2. Confirm MPLS is configured and active
    Check the device configuration for MPLS protocol settings. On Junos, this typically appears under 'protocols mpls' in the configuration.
    Affected if MPLS is configured and operational - the attack vector specifically requires sending the malformed packet over an MPLS transit path.
  3. Determine the installed Junos OS version
    Use the command to display the running Junos version (such as 'show version' or equivalent). Compare the exact version number against the affected ranges: Junos versions < 12.3, = 12.3, = 12.3r12, = 15.1, = 17.3, = 18.3, = 18.4, = 19.1, = 19.2, = 19.3, = 19.4, = 20.1; or Junos Os Evolved versions < 20.4, = 20.4, = 21.2, = 21.3, = 21.4.
    Affected if The installed version exactly matches one of the listed affected versions or falls within the specified version ranges.
  4. Confirm the device has IPv6 and MPLS simultaneously active
    Review both the IPv6 and MPLS configuration states to determine if both are concurrently enabled on the device.
    Affected if Both IPv6 and MPLS are simultaneously enabled - the vulnerability only manifests when IPv6 traffic can traverse an MPLS path.

The device is affected by CVE-2022-22214 only if it runs a vulnerable Junos or Junos Evolved version AND has both IPv6 and MPLS enabled concurrently; if IPv6 is disabled or the version is not in the affected list, the device is not vulnerable to this specific flaw.

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
Upgrade available Upgrade to 12.3 / 20.4 or later
Fixed in 12.320.4
Interim mitigation

Apply the vendor-supplied patches for the specific Junos OS/Evolved version or, as a compensating control, disable IPv6 if not required and implement MPLS access controls to limit exposure to adjacent attackers.

Recommended fix High confidence

Upgrade to the appropriate fixed release for the version branch: 12.3R12-S21, 15.1R7-S10, 17.3R3-S12, 18.3R3-S6, 18.4R2-S9, 19.1R3-S7, 19.2R3-S3, 19.3R3-S4, 19.4R3-S5, 20.1R3, 20.2R3-S2, 20.3R3, 20.4R3, 21.1R2 or later for Junos OS; or 20.4R3-S3-EVO, 21.2R3-EVO, 21.3R3-EVO, 21.4R2-EVO or later for J

  1. 1. Identify the current Junos OS or Junos OS Evolved version running on the device using the command: `show version`
  2. 2. Determine the appropriate upgrade path based on the current version branch (12.3, 15.1, 17.3, 18.3, 18.4, 19.x, 20.x, 21.x)
  3. 3. Download the corresponding fixed release from the Juniper Networks support portal: for 12.3 upgrade to 12.3R12-S21 or later; for 15.1 upgrade to 15.1R7-S10 or later; for 17.3 upgrade to 17.3R3-S12 or later; for 18.3 upgrade to 18.3R3-S6 or later; for 18.4 upgrade to 18.4R2-S9 or later; for 19.1 upgrade to 19.1R3-S7 or later; for 19.2 upgrade to 19.2R3-S3 or later; for 19.3 upgrade to 19.3R3-S4
  4. 4. For Junos OS Evolved: upgrade to 20.4R3-S3-EVO, 21.2R3-EVO, 21.3R3-EVO, or 21.4R2-EVO or later
  5. 5. Upload the upgrade package to the device and initiate the upgrade using: `request system software add <package-name>`
  6. 6. After upgrade completes, reboot the device using: `request system reboot`
  7. 7. Verify the upgrade was successful and the fix is applied using: `show version` and confirm the new version includes the fix
  8. 8. As an alternative mitigation (if upgrade is not immediately possible), disable IPv6 over MPLS on interfaces where MPLS is configured if IPv6 is not required, using: `delete protocols mpls interface <interface-name>` or by restricting IPv6 traffic at the interface level
Caveat Standard Junos upgrade risks apply - ensure to review Junos upgrade guide, test in lab environment first, and verify compatibility with any existing configurations and third-party integrations

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 / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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