dbcve.org
JunosOperating system · Juniper

CVE-2022-22219

MEDIUM · 5.9 CVSS v3.1 Published 2022-10-18
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
Due to the Improper Handling of an Unexpected Data Type in the processing of EVPN routes on Juniper Networks Junos OS and Junos OS Evolved, an attacker in direct control of a BGP client connected to a route reflector, or via a machine in the middle (MITM) attack, can send a specific EVPN route contained within a BGP Update, triggering a routing protocol daemon (RPD) crash, leading to a Denial of Service (DoS) condition. Continued receipt and processing of these specific EVPN routes could create a sustained Denial of Service (DoS) condition. This issue only occurs on BGP route reflectors, only within a BGP EVPN multicast environment, and only when one or more BGP clients have 'leave-sync-route-oldstyle' enabled. This issue affects: Juniper Networks Junos OS 21.3 versions prior to 21.3R3-S2; 21.4 versions prior to 21.4R2-S2, 21.4R3; 22.1 versions prior to 22.1R1-S2, 22.1R3; 22.2 versions prior to 22.2R2. Juniper Networks Junos OS Evolved 21.3 version 21.3R1-EVO and later versions prior to 21.4R3-EVO; 22.1 versions prior to 22.1R1-S2-EVO, 22.1R3-EVO; 22.2 versions prior to 22.2R2-EVO. This issue does not affect: Juniper Networks Junos OS versions prior to 21.3R1. Juniper Networks Junos OS Evolved versions prior to 21.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 vulnerability in Juniper Junos OS and Junos OS Evolved allows an attacker to crash the routing protocol daemon (RPD) by sending a specially crafted EVPN route within a BGP Update message. This only affects BGP route reflectors in BGP EVPN multicast environments where 'leave-sync-route-oldstyle' is enabled, causing a Denial of Service condition.

MitigationUpgrade to the specified Junos OS versions (21.3R3-S2, 21.4R2-S2/21.4R3, 22.1R1-S2/22.1R3, 22.2R2 or later) or Junos OS Evolved versions (21.4R3-EVO, 22.1R1-S2-EVO/22.1R3-EVO, 22.2R2-EVO or later). Alternatively, disable the 'leave-sync-route-oldstyle' configuration option if the environment allows.

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.3= 21.4= 22.1= 22.2
Junos Os EvolvedOperating system
Affected:= 21.3= 22.1= 22.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
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. Verify Junos OS version
    Run 'show version' command and compare the installed version against the affected ranges: Junos 21.3, 21.4, 22.1, 22.2 or Junos OS Evolved 21.3, 22.1, 22.2
    Affected if The device runs any of the listed affected versions without the fixed patches applied
  2. Confirm BGP route reflector role
    Run 'show bgp summary' or 'show configuration protocols bgp' to determine if the device is configured as a BGP route reflector (look for 'cluster' configuration or 'route-reflector-client' statements)
    Affected if The device is configured as a BGP route reflector handling EVPN routes
  3. Check for EVPN multicast configuration
    Run 'show configuration protocols evpn' and look for multicast-related configuration such as 'multicast-mode' or EVPN instance configurations
    Affected if BGP EVPN with multicast is configured on the device
  4. Verify leave-sync-route-oldstyle is enabled
    Run 'show configuration protocols bgp' | match leave-sync-route-oldstyle' or check the BGP configuration hierarchy under 'protocols bgp group <name> evpn' for the 'leave-sync-route-oldstyle' statement
    Affected if The 'leave-sync-route-oldstyle' configuration option is explicitly enabled

A device is affected if it runs an affected Junos version, is configured as a BGP route reflector with EVPN multicast, and has 'leave-sync-route-oldstyle' enabled, making it vulnerable to RPD crashes from specially crafted EVPN routes.

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 to the specified Junos OS versions (21.3R3-S2, 21.4R2-S2/21.4R3, 22.1R1-S2/22.1R3, 22.2R2 or later) or Junos OS Evolved versions (21.4R3-EVO, 22.1R1-S2-EVO/22.1R3-EVO, 22.2R2-EVO or later). Alternatively, disable the 'leave-sync-route-oldstyle' configuration option if the environment allows.

Recommended fix High confidence

Junos OS: 21.3R3-S2, 21.4R2-S2/21.4R3, 22.1R1-S2/22.1R3, or 22.2R2 | Junos OS Evolved: 21.4R3-EVO, 22.1R1-S2-EVO/22.1R3-EVO, or 22.2R2-EVO

  1. 1. Identify all BGP route reflectors running affected Junos OS or Junos OS Evolved versions (21.3, 21.4, 22.1, 22.2)
  2. 2. Verify if the device is configured as a BGP route reflector with EVPN multicast and has 'leave-sync-route-oldstyle' configured under BGP client(s)
  3. 3. Schedule a maintenance window for the upgrade
  4. 4. Back up the current configuration
  5. 5. Upgrade Junos OS to one of: 21.3R3-S2 or later, 21.4R2-S2/21.4R3 or later, 22.1R1-S2/22.1R3 or later, or 22.2R2 or later
  6. 6. For Junos OS Evolved, upgrade to one of: 21.4R3-EVO or later, 22.1R1-S2-EVO/22.1R3-EVO or later, or 22.2R2-EVO or later
  7. 7. Verify the RPD process is running stably after upgrade
  8. 8. Monitor for any unexpected RPD restarts
Caveat Standard Junos upgrade considerations apply; ensure compatibility with other network devices and review release notes for any known issues

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

Fix this in Junos Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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