dbcve.org
JunosOperating system · Juniper

CVE-2022-22196

MEDIUM · 6.5 CVSS v3.1 Published 2022-04-14
Fix available
A fix is available. Upgrade to 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 Check for Unusual or Exceptional Conditions vulnerability in the Routing Protocol Daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an adjacent, unauthenticated attacker with an established ISIS adjacency to cause a Denial of Service (DoS). The rpd CPU spikes to 100% after a malformed ISIS TLV has been received which will lead to processing issues of routing updates and in turn traffic impact. This issue affects: Juniper Networks Junos OS 19.3 versions prior to 19.3R3-S4; 19.4 versions prior to 19.4R2-S6, 19.4R3-S6; 20.1 versions prior to 20.1R3-S2; 20.2 versions prior to 20.2R3-S3; 20.3 versions prior to 20.3R3-S1; 20.4 versions prior to 20.4R3; 21.1 versions prior to 21.1R3; 21.2 versions prior to 21.2R2. Juniper Networks Junos OS Evolved All versions prior to 20.4R3-S3-EVO; 21.2 versions prior to 21.2R2-EVO. This issue does not affect Juniper Networks Junos OS versions prior to 19.3R1.

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 malformed ISIS TLV triggers an improper check for unusual conditions in the Routing Protocol Daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved. When an adjacent, unauthenticated attacker with an established ISIS adjacency sends this crafted packet, the rpd process consumes 100% CPU, preventing routing update processing and causing traffic disruption.

MitigationUpgrade Junos OS/Evolved to the specified patched versions. If immediate patching is not possible, consider isolating ISIS-speaking neighbors or implementing route filtering/ACLs to limit ISIS adjacency to trusted segments.

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.3= 19.4= 20.1= 20.2= 20.3= 20.4= 21.1= 21.2
Junos Os EvolvedOperating system
Affected:< 20.4= 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. Check Junos OS version
    Run 'show version' or 'request system version' to obtain the installed Junos OS version
    Affected if The version matches 19.3, 19.4, 20.1, 20.2, 20.3, 20.4, 21.1, or 21.2 (for Junos) or is below 20.4, equals 20.4, or equals 21.2 (for Junos OS Evolved)
  2. Verify ISIS protocol is enabled
    Run 'show protocol isis' or check the configuration with 'show configuration protocols isis'
    Affected if ISIS protocol is configured and enabled on the device, exposing the attack surface
  3. List active ISIS adjacencies
    Run 'show isis adjacency' to see all established ISIS neighbors
    Affected if There are active ISIS adjacencies, particularly from untrusted or unexpected neighbors
  4. Check rpd process CPU usage
    Run 'show system processes rpd' or 'monitor system processes rpd' to observe CPU consumption
    Affected if The rpd process is consuming 100% CPU or showing abnormally high CPU usage
  5. Review ISIS interface configuration
    Run 'show isis interface' to see which interfaces have ISIS enabled
    Affected if ISIS is enabled on interfaces connected to untrusted network segments

The device is affected if it runs a vulnerable Junos version with ISIS enabled and has active adjacencies, especially if rpd shows abnormal CPU usage.

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 20.4 or later
Fixed in 20.4
Interim mitigation

Upgrade Junos OS/Evolved to the specified patched versions. If immediate patching is not possible, consider isolating ISIS-speaking neighbors or implementing route filtering/ACLs to limit ISIS adjacency to trusted segments.

Recommended fix High confidence

Junos OS 21.2R2 or later / Junos OS Evolved 21.2R2-EVO or later

  1. 1. Identify the current Junos OS or Junos OS Evolved version running on the device using 'show version'
  2. 2. Confirm ISIS protocol is in use with 'show isis adjacency'
  3. 3. Plan maintenance window as upgrade will require a system restart
  4. 4. Download the appropriate fixed release from Juniper Networks (21.2R2 or later recommended)
  5. 5. Upload the Junos upgrade package to the device using SCP or FTP
  6. 6. Run 'request system software add <package-name>' to install the upgrade
  7. 7. Reboot the device using 'request system reboot' after installation completes
  8. 8. After reboot, verify the new version with 'show version' and confirm ISIS adjacency is restored with 'show isis adjacency'
Caveat Upgrade requires a system reboot which will cause brief network disruption; ensure high availability redundancy is in place or plan maintenance window

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 / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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