dbcve.org
Junos Os EvolvedOperating system · Juniper

CVE-2022-22197

HIGH · 7.5 CVSS v3.1 Published 2022-04-14
Fix available
A fix is available. Upgrade to 17.3 / 20.1 or later.
See remediation →
84/100
Remediation priority · High
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
An Operation on a Resource after Expiration or Release vulnerability in the Routing Protocol Daemon (RPD) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated network-based attacker with an established BGP session to cause a Denial of Service (DoS). This issue occurs when proxy-generate route-target filtering is enabled, and certain proxy-route add and delete events are happening. This issue affects: Juniper Networks Junos OS All versions prior to 17.3R3-S11; 17.4 versions prior to 17.4R2-S13, 17.4R3-S4; 18.3 versions prior to 18.3R3-S4; 18.4 versions prior to 18.4R1-S8, 18.4R2-S8, 18.4R3-S6; 19.1 versions prior to 19.1R3-S4; 19.2 versions prior to 19.2R1-S6, 19.2R3-S2; 19.3 versions prior to 19.3R2-S6, 19.3R3-S1; 19.4 versions prior to 19.4R1-S4, 19.4R2-S4, 19.4R3; 20.1 versions prior to 20.1R2; 20.2 versions prior to 20.2R2; 20.3 versions prior to 20.3R1-S2, 20.3R2. Juniper Networks Junos OS Evolved All versions prior to 20.1R3-EVO; 20.2 versions prior to 20.2R3-EVO; 20.3 versions prior to 20.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

Use-after-free vulnerability in the Routing Protocol Daemon (RPD) of Juniper Junos OS and Junos OS Evolved. An unauthenticated network-based attacker with an established BGP session can cause a Denial of Service by exploiting the vulnerability when proxy-generate route-target filtering is enabled and certain proxy-route add/delete events occur, leading to the RPD process crashing.

MitigationApply the appropriate Juniper-supplied Junos OS/Evolved software update from the advisory. If patching is delayed, consider disabling proxy-generate route-target filtering if not operationally required, or implement network-level controls to limit BGP session exposure to untrusted peers.

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
Junos Os EvolvedOperating system
Affected:< 20.1= 20.1= 20.2= 20.3
JunosOperating system
Affected:< 17.3= 17.3= 17.4= 18.3= 18.4= 19.1= 19.2= 19.3= 19.4= 20.1= 20.2= 20.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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/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 'show version detail' to obtain the installed Junos OS or Junos OS Evolved version number
    Affected if The installed version matches any of the affected versions listed: Junos OS Evolved < 20.1, = 20.1, = 20.2, = 20.3; or Junos OS < 17.3, = 17.3, = 17.4, = 18.3, = 18.4, = 19.1, = 19.2, = 19.3, = 19.4, = 20.1, = 20.2, = 20.3
  2. Verify BGP is configured and sessions exist
    Run 'show bgp summary' or 'show bgp neighbor' to confirm BGP is enabled and there are established BGP peer sessions
    Affected if BGP is configured and active sessions exist with untrusted peers
  3. Confirm proxy-generate route-target filtering is enabled
    Run 'show configuration protocols bgp' and look for 'proxy-generate route-target-filter' under the BGP configuration, or check the routing instance configuration with 'show configuration routing-instances <instance-name> protocols bgp'
    Affected if Proxy-generate route-target filtering is configured and enabled in the BGP or routing instance configuration
  4. Check RPD process status
    Run 'show system processes rpd' or 'show system processes extensive | match rpd' to verify the Routing Protocol Daemon is running
    Affected if The RPD process is not running or has recently crashed, indicating potential exploitation

The environment is affected if the Junos version is in the affected list AND proxy-generate route-target filtering is enabled AND there are active BGP sessions that could be exploited by an unauthenticated attacker.

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 17.3 / 20.1 or later
Fixed in 17.320.1
Interim mitigation

Apply the appropriate Juniper-supplied Junos OS/Evolved software update from the advisory. If patching is delayed, consider disabling proxy-generate route-target filtering if not operationally required, or implement network-level controls to limit BGP session exposure to untrusted peers.

Recommended fix High confidence

Upgrade to Junos OS 17.3R3-S11+/17.4R2-S13+/17.4R3-S4+/18.3R3-S4+/18.4R3-S6+/19.1R3-S4+/19.2R3-S2+/19.3R3-S1+/19.4R3+/20.1R2+/20.2R2+/20.3R2+ or Junos OS Evolved 20.1R3-EVO+/20.2R3-EVO+/20.3R2-EVO+

  1. 1. Identify the current Junos OS or Junos OS Evolved version running on the device using 'show version' or 'show version detail'.
  2. 2. Identify whether proxy-generate route-target filtering is enabled using 'show configuration protocols bgp' and looking for 'proxy-generate' or 'route-target' filtering configuration.
  3. 3. Plan an upgrade to a fixed release based on the current branch: for Junos OS 17.3.x upgrade to 17.3R3-S11 or later; 17.4.x upgrade to 17.4R2-S13 or 17.4R3-S4 or later; 18.3.x upgrade to 18.3R3-S4 or later; 18.4.x upgrade to 18.4R3-S6 or later (or 18.4R1-S8/18.4R2-S8); 19.1.x upgrade to 19.1R3-S4 or later; 19.2.x upgrade to 19.2R3-S2 or later; 19.3.x upgrade to 19.3R3-S1 or later; 19.4.x upgrade
  4. 4. For Junos OS Evolved: 20.1.x upgrade to 20.1R3-EVO or later; 20.2.x upgrade to 20.2R3-EVO or later; 20.3.x upgrade to 20.3R2-EVO or later.
  5. 5. Before upgrading, backup the current configuration using 'request system configuration rescue save' or 'show configuration | save' to a remote location.
  6. 6. Schedule a maintenance window as the upgrade will require a system reboot.
  7. 7. Download the appropriate Junos software package from the Juniper Networks support portal (kb.juniper.net).
  8. 8. Upload the software to the device using 'request system software add <package>' with appropriate options.
Caveat Standard Junos upgrade considerations apply - review release notes for any configuration changes or deprecated features; ensure compatibility with other devices in the network

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

Fix this in Junos Os Evolved Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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