dbcve.org
JunosOperating system · Juniper

CVE-2022-22208

MEDIUM · 5.9 CVSS v3.1 Published 2022-10-18
Fix available
A fix is available. Upgrade to 18.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 Use After Free vulnerability in the Routing Protocol Daemon (rdp) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated network-based attacker to cause Denial of Service (DoS). When a BGP session flap happens, a Use After Free of a memory location that was assigned to another object can occur, which will lead to an rpd crash. This is a race condition that is outside of the attacker's control and cannot be deterministically exploited. Continued flapping of BGP sessions can create a sustained Denial of Service (DoS) condition. This issue affects Juniper Networks Junos OS: All versions prior to 18.4R2-S9, 18.4R3-S11; 19.1 versions prior to 19.1R3-S8; 19.2 version 19.2R1 and later versions; 19.3 versions prior to 19.3R3-S5; 19.4 versions prior to 19.4R2-S6, 19.4R3-S6; 20.1 version 20.1R1 and later versions; 20.2 versions prior to 20.2R3-S3; 20.3 versions prior to 20.3R3-S2; 20.4 versions prior to 20.4R3-S1; 21.1 versions prior to 21.1R3-S3; 21.2 versions prior to 21.2R2-S1, 21.2R3. Juniper Networks Junos OS Evolved All versions prior to 20.4R3-S4-EVO; 21.1-EVO versions prior to 21.1R3-S2-EVO; 21.2-EVO versions prior to 21.2R3-EVO; 21.3-EVO versions prior to 21.3R2-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 Use After Free vulnerability exists in the Routing Protocol Daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved. When BGP sessions flap, a race condition causes memory that was freed to be accessed again, leading to rpd crash and denial of service. This is a non-deterministic race condition that cannot be reliably exploited but can be triggered by repeated BGP session instability.

MitigationUpgrade Junos OS/Evo to a version beyond the fixed releases (19.2R1+, 20.4R3-S1+, 21.1R3-S3+, 21.2R2-S1+, etc.) or implement BGP route flap damping to reduce session instability and minimize crash triggers.

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:< 18.4= 18.4= 19.1= 19.2= 19.3= 19.4= 20.1= 20.2= 20.3= 20.4= 21.1= 21.2
Junos Os EvolvedOperating system
Affected:= 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 product and version
    Run 'show version' or 'show version detail' to obtain the exact Junos OS or Junos OS Evolved version running on the device
    Affected if The version matches any of the following: Junos < 18.4, or versions 18.4, 19.1, 19.2, 19.3, 19.4, 20.1, 20.2, 20.3, 20.4, 21.1, 21.2 for Junos OS; or versions 21.1, 21.2, 21.3 for Junos OS Evolved
  2. Confirm BGP is configured
    Run 'show configuration protocols bgp' to check if BGP is enabled and configured on the device
    Affected if BGP is actively configured and running, as the vulnerability triggers through BGP session flapping in the rpd process
  3. Check for BGP route damping configuration
    Run 'show configuration protocols bgp' and look for 'damping' statements under BGP peer or group configurations, or run 'show bgp damping'
    Affected if BGP damping is NOT configured, as the lack of damping allows frequent session flaps that can trigger the race condition more readily
  4. Monitor rpd process stability
    Run 'show system processes rpd' or check 'show system core-dumps' for any recent rpd crash logs, and review 'show log messages' for rpd crash indications
    Affected if Recent rpd crashes or core dumps are present, which could indicate this vulnerability has been triggered
  5. Verify if BGP sessions are experiencing instability
    Run 'show bgp summary' repeatedly over time or review BGP logs for session state changes, flapping events, and peer resets
    Affected if BGP sessions are frequently flapping or resetting, which is the condition that can trigger the use-after-free race condition in rpd

A device is affected if it runs a vulnerable Junos OS or Junos OS Evolved version (18.4 through 21.2 for OS, 21.1-21.3 for Evolved), has BGP configured, and experiences BGP session instability that could trigger the race condition in the rpd process.

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

Upgrade Junos OS/Evo to a version beyond the fixed releases (19.2R1+, 20.4R3-S1+, 21.1R3-S3+, 21.2R2-S1+, etc.) or implement BGP route flap damping to reduce session instability and minimize crash triggers.

Recommended fix High confidence

Minimum fixed versions per branch: 18.4R3-S11 (or 18.4R2-S9), 19.1R3-S8, 19.4R3-S6, 20.4R3-S1, 21.1R3-S3, 21.2R3, 21.3R2-EVO; Evolved: 20.4R3-S4-EVO, 21.1R3-S2-EVO, 21.2R3-EVO, 21.3R2-EVO

  1. 1. Identify the current Junos OS or Junos OS Evolved version running on the affected device using 'show version'
  2. 2. Based on the current version branch, plan upgrade to the minimum fixed release: For 18.4 branch, upgrade to 18.4R3-S11 or later (or 18.4R2-S9 or later); For 19.1 branch, upgrade to 19.1R3-S8 or later; For 19.2/19.3/19.4 branch, upgrade to 19.4R3-S6 or later; For 20.1/20.2/20.3/20.4 branch, upgrade to 20.4R3-S1 or later; For 21.1 branch, upgrade to 21.1R3-S3 or later; For 21.2 branch, upgrade to
  3. 3. Download the appropriate Junos upgrade image from the Juniper Networks support portal (kb.juniper.net)
  4. 4. Back up the current configuration using 'request system snapshot'
  5. 5. Initiate the upgrade using 'request system software add <package_name>' with the appropriate reboot option
  6. 6. After upgrade completes, verify the new version with 'show version' and confirm BGP neighbors are stable using 'show bgp summary'
Caveat Review Junos OS upgrade guide for potential compatibility issues; ensure configuration compatibility between major versions; Evolved to OS upgrades require careful planning as they are distinct platforms

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

Fix this in Junos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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