dbcve.org
JunosOperating system · Juniper

CVE-2022-22213

MEDIUM · 5.9 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 →
68/100
Remediation priority · Elevated
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
A vulnerability in Handling of Undefined Values in the routing protocol daemon (RPD) process of Juniper Networks Junos OS and Junos OS Evolved may allow an unauthenticated network-based attacker to crash the RPD process by sending a specific BGP update while the system is under heavy load, leading to a Denial of Service (DoS). Continued receipt and processing of this packet will create a sustained Denial of Service (DoS) condition. Malicious exploitation of this issue requires a very specific combination of load, timing, and configuration of the vulnerable system which is beyond the direct control of the attacker. Internal reproduction has only been possible through artificially created load and specially instrumented source code. Systems are only vulnerable to this issue if BGP multipath is enabled. Routers not configured for BGP multipath are not vulnerable to this issue. This issue affects: Juniper Networks Junos OS: 21.1 versions prior to 21.1R3-S1; 21.2 versions prior to 21.2R2-S2, 21.2R3; 21.3 versions prior to 21.3R2, 21.3R3; 21.4 versions prior to 21.4R1-S1, 21.4R2. Juniper Networks Junos OS Evolved: 21.1 versions prior to 21.1R3-S1-EVO; 21.2 version 21.2R1-EVO and later versions; 21.3 versions prior to 21.3R3-EVO; 21.4 versions prior to 21.4R1-S1-EVO, 21.4R2-EVO. This issue does not affect: Juniper Networks Junos OS versions prior to 21.1. Juniper Networks Junos OS Evolved versions prior to 21.1-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 vulnerability in the routing protocol daemon (RPD) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated network-based attacker to crash the RPD process by sending a specific BGP update while the system is under heavy load. The attack requires BGP multipath to be enabled and a very specific combination of load and timing, making exploitation difficult in practice.

MitigationEnable BGP multipath only if operationally required; disabling BGP multipath eliminates the vulnerability. Alternatively, upgrade to the fixed versions (21.1R3-S1, 21.2R2-S2/21.2R3, 21.3R2-S1/21.3R3, 21.4R1-S1/21.4R2 or later) for Junos OS, or corresponding EVO versions.

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:= 21.1= 21.2= 21.3= 21.4
Junos Os EvolvedOperating system
Affected:= 21.1= 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
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/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. Determine installed Junos version
    Run 'show version' on the device CLI to retrieve the installed Junos OS version
    Affected if The version displayed is 21.1, 21.2, 21.3, or 21.4 (exact match)
  2. Check if BGP multipath is enabled
    Run 'show configuration protocols bgp' and look for 'multipath' or 'multipath-multiple-as' under the BGP hierarchy or BGP group configuration
    Affected if BGP multipath feature is configured and enabled in the BGP protocol settings
  3. Confirm RPD daemon is running
    Run 'show routing daemon' or 'ps aux | grep rpd' to verify the routing protocol daemon process is active
    Affected if RPD is running and the device meets both version and BGP multipath conditions

A user is affected if their Junos device runs version 21.1, 21.2, 21.3, or 21.4 AND has BGP multipath enabled in the configuration.

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

Enable BGP multipath only if operationally required; disabling BGP multipath eliminates the vulnerability. Alternatively, upgrade to the fixed versions (21.1R3-S1, 21.2R2-S2/21.2R3, 21.3R2-S1/21.3R3, 21.4R1-S1/21.4R2 or later) for Junos OS, or corresponding EVO versions.

Recommended fix High confidence

Junos OS: 21.1R3-S1, 21.2R2-S2/21.2R3, 21.3R2/21.3R3, 21.4R1-S1/21.4R2 or later; Junos OS Evolved: 21.1R3-S1-EVO, 21.2R3-EVO, 21.3R3-EVO, 21.4R1-S1-EVO/21.4R2-EVO or later

  1. 1. Verify the current Junos OS or Junos OS Evolved version by running 'show version' or 'show version detail'
  2. 2. Identify whether BGP multipath is enabled by running 'show configuration protocols bgp' and checking for 'multipath' or 'multipath multiple-as'
  3. 3. Determine the appropriate upgrade path based on your current version: For Junos OS 21.1.x upgrade to 21.1R3-S1 or later; 21.2.x upgrade to 21.2R2-S2, 21.2R3, or later; 21.3.x upgrade to 21.3R2, 21.3R3, or later; 21.4.x upgrade to 21.4R1-S1, 21.4R2, or later
  4. 4. For Junos OS Evolved: 21.1.x upgrade to 21.1R3-S1-EVO or later; 21.2.x upgrade to 21.2R3-EVO or later; 21.3.x upgrade to 21.3R3-EVO or later; 21.4.x upgrade to 21.4R1-S1-EVO, 21.4R2-EVO, or later
  5. 5. Schedule a maintenance window as upgrade requires system reboot
  6. 6. Download the appropriate upgrade package from the Juniper Networks support portal
  7. 7. Follow standard Junos upgrade procedure: 'request system software add <package> reboot'
  8. 8. After upgrade, verify BGP multipath configuration is still functioning correctly
Caveat Standard Junos upgrade risks apply - ensure configuration compatibility and have rollback plan; this is a minor version upgrade within the same release train

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 help mitigating

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-22213 — 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-22213 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