dbcve.org
JunosOperating system · Juniper

CVE-2022-22225

MEDIUM · 5.9 CVSS v3.1 Published 2022-10-18
Fix available
A fix is available. Upgrade to 20.4 or later.
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 Time-of-check Time-of-use (TOCTOU) Race Condition vulnerability in the Routing Protocol Daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated attacker with an established BGP session to cause a Denial of Service (DoS). In a BGP multipath scenario, when one of the contributing routes is flapping often and rapidly, rpd may crash. As this crash depends on whether a route is a contributing route, and on the internal timing of the events triggered by the flap this vulnerability is outside the direct control of a potential attacker. This issue affects: Juniper Networks Junos OS 19.2 versions prior to 19.2R3-S6; 20.2 versions prior to 20.2R3-S4; 20.3 versions prior to 20.3R3-S3; 20.4 versions prior to 20.4R3-S4; 21.1 versions prior to 21.1R3; 21.2 versions prior to 21.2R2; 21.3 versions prior to 21.3R2. Juniper Networks Junos OS Evolved All versions prior to 20.4R3-S4-EVO; 21.1-EVO version 21.1R1-EVO and later versions; 21.2-EVO versions prior to 21.2R2-EVO; 21.3-EVO versions prior to 21.3R2-EVO. This issue does not affect: Juniper Networks Junos OS versions 19.2 versions prior to 19.2R2, 19.3R1 and above prior to 20.2R1. Juniper Networks Junos OS Evolved versions prior to 20.2R1-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 TOCTOU race condition in Juniper's rpd daemon allows an unauthenticated attacker with an established BGP session to cause a denial of service. In BGP multipath scenarios, when a contributing route flaps rapidly, the race condition between route state checking and usage can trigger an rpd crash due to timing-dependent internal event handling.

MitigationApply the vendor-supplied patches for Junos OS (19.2R3-S6, 20.2R3-S4, 20.3R3-S3, 20.4R3-S4, 21.1R3, 21.2R2, 21.3R2 and later) or Junos OS Evolved (20.4R3-S4-EVO, 21.1R1-EVO and later, 21.2R2-EVO, 21.3R2-EVO and later) to address 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.2= 20.2= 20.3= 20.4= 21.1= 21.2= 21.3
Junos Os EvolvedOperating system
Affected:< 20.4= 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
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. Identify Junos version
    Run `show version` or `show version detail` to obtain the installed Junos OS or Junos OS Evolved version number.
    Affected if Version matches 19.2, 20.2, 20.3, 20.4, 21.1, 21.2, or 21.3 without the vendor-supplied patched versions (19.2R3-S6, 20.2R3-S4, 20.3R3-S3, 20.4R3-S4, 21.1R3, 21.2R2, 21.3R2 or later for Junos; 20.4R3-S4-EVO, 21.1R1-EVO and later, 21.2R2-EVO, 21.3R2-EVO or later for Junos OS Evolved).
  2. Verify BGP is configured
    Run `show configuration protocols bgp` to check if BGP protocol is configured on the device.
    Affected if BGP is actively configured and the device accepts BGP sessions.
  3. Confirm BGP multipath is enabled
    Run `show configuration protocols bgp group <group-name>` or `show configuration protocols bgp` and look for the `multipath` or `multipath-multiple-as` configuration statement under the BGP group or neighbor hierarchy.
    Affected if BGP multipath feature is explicitly configured, as the vulnerability only triggers in multipath scenarios.
  4. Check for rpd crash history
    Run `show system core-dumps` or review `/var/crash/` directory for any rpd core dump files that may indicate a past crash event.
    Affected if Recent rpd crashes exist that correlate with BGP multipath route flapping events.

A device is affected if it runs a vulnerable Junos version without the fixed patches AND has BGP multipath actively configured, making it susceptible to the race condition when a BGP contributing route flaps rapidly.

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

Apply the vendor-supplied patches for Junos OS (19.2R3-S6, 20.2R3-S4, 20.3R3-S3, 20.4R3-S4, 21.1R3, 21.2R2, 21.3R2 and later) or Junos OS Evolved (20.4R3-S4-EVO, 21.1R1-EVO and later, 21.2R2-EVO, 21.3R2-EVO and later) to address this vulnerability.

Recommended fix High confidence

19.2R3-S6 (or later 19.2), 20.2R3-S4 (or later 20.2), 20.3R3-S3 (or later 20.3), 20.4R3-S4 (or later 20.4), 21.1R3 (or later 21.1), 21.2R2 (or later 21.2), 21.3R2 (or later 21.3); Junos OS Evolved: 20.4R3-S4-EVO, 21.2R2-EVO, 21.3R2-EVO

  1. 1. Identify the current Junos OS or Junos OS Evolved version running on the device using 'show version'
  2. 2. Determine the appropriate upgrade path based on the current version branch (19.2, 20.2, 20.3, 20.4, 21.1, 21.2, or 21.3)
  3. 3. Download the corresponding fixed release from the Juniper Networks support portal: 19.2R3-S6, 20.2R3-S4, 20.3R3-S3, 20.4R3-S4, 21.1R3, 21.2R2, or 21.3R2 for Junos OS; 20.4R3-S4-EVO, 21.2R2-EVO, or 21.3R2-EVO for Junos OS Evolved
  4. 4. Plan maintenance window as upgrade requires system reboot
  5. 5. Upload the Junos upgrade package to the device
  6. 6. Execute upgrade using 'request system software add <package>' command
  7. 7. Verify the upgrade completed successfully and the device is running the fixed version
  8. 8. Confirm BGP multipath functionality is operating normally post-upgrade
Caveat Standard Junos upgrade considerations apply - review Junos upgrade guide for compatibility, ensure configuration backup, and plan for potential rollback if issues arise

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

Fix this in Junos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
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,080.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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