dbcve.org
JunosOperating system · Juniper

CVE-2022-22193

MEDIUM · 5.5 CVSS v3.1 Published 2022-04-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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 Handling of Unexpected Data Type vulnerability in the Routing Protocol Daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows a locally authenticated attacker with low privileges to cause a Denial of Service (DoS). Continued execution of this command might cause a sustained Denial of Service condition. If BGP rib sharding is configured and a certain CLI command is executed the rpd process can crash. During the rpd crash and restart, the routing protocols might be impacted and traffic disruption might be seen due to the loss of routing information. This issue affects: Juniper Networks Junos OS 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 20.4 versions prior to 20.4R3-EVO; 21.1 versions prior to 21.1R3-EVO; 21.2 versions prior to 21.2R2-EVO. This issue does not affect: Juniper Networks Junos OS versions prior to 20.3R1. Juniper Networks Junos OS Evolved versions prior to 20.3R1-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

A data type handling flaw in the Routing Protocol Daemon (rpd) allows a locally authenticated low-privilege attacker to crash rpd when BGP rib sharding is configured and a specific CLI command is executed, causing DoS.

MitigationUpgrade Junos OS/Evolved to patched versions (20.3R3-S1, 20.4R3, 21.1R3, 21.2R2 or later); avoid executing the triggering CLI command if upgrade is not immediately feasible.

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.1= 21.2
Junos Os EvolvedOperating system
Affected:= 20.4= 21.1= 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 version
    Run 'show version' command or check system banner to identify the installed Junos version
    Affected if Version is 20.3, 20.4, 21.1, or 21.2 (for Junos) or 20.4, 21.1, or 21.2 (for Junos Evolved)
  2. Confirm BGP rib sharding configuration
    Run 'show configuration protocols bgp | display set' or inspect the BGP configuration for rib-sharding related statements
    Affected if BGP rib sharding is explicitly configured in the device configuration
  3. Verify rpd process status
    Run 'show system processes extensive | match rpd' or 'ps -aux | grep rpd' to confirm the routing protocol daemon is running
    Affected if rpd is running (which is normal but confirms the target process exists for exploitation)

Environment is affected if running an affected Junos version (20.3, 20.4, 21.1, 21.2 for Junos or 20.4, 21.1, 21.2 for Junos Evolved) AND BGP rib sharding is configured, making the device vulnerable to a DoS via the specific triggering CLI command.

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/Evolved to patched versions (20.3R3-S1, 20.4R3, 21.1R3, 21.2R2 or later); avoid executing the triggering CLI command if upgrade is not immediately feasible.

Recommended fix High confidence

Junos OS: 20.3R3-S1, 20.4R3, 21.1R3, or 21.2R2 (or later); Junos OS Evolved: 20.4R3-EVO, 21.1R3-EVO, or 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. For Junos OS: If running 20.3x, upgrade to 20.3R3-S1 or later; if running 20.4x, upgrade to 20.4R3 or later; if running 21.1x, upgrade to 21.1R3 or later; if running 21.2x, upgrade to 21.2R2 or later
  3. 3. For Junos OS Evolved: If running 20.4x, upgrade to 20.4R3-EVO or later; if running 21.1x, upgrade to 21.1R3-EVO or later; if running 21.2x, upgrade to 21.2R2-EVO or later
  4. 4. Download the appropriate Junos upgrade package from the Juniper Networks support portal ensuring it matches your exact hardware model
  5. 5. Backup the current configuration using 'request system snapshot' or by exporting the configuration
  6. 6. Upload the upgrade package to the device and initiate the upgrade using 'request system software add <package>'
  7. 7. Reboot the device after successful installation using 'request system reboot'
  8. 8. Verify the new version is installed and rpd is running normally using 'show version' and 'show routing-engine'
Caveat Standard Junos upgrade considerations apply - review Junos upgrade guide for compatibility and ensure configuration compatibility with target release

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

Fix this in Junos Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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