dbcve.org
JunosOperating system · Juniper

CVE-2022-22166

MEDIUM · 6.5 CVSS v3.1 Published 2022-01-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
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 Improper Validation of Specified Quantity in Input vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS allows an unauthenticated networked attacker to cause an rdp crash and thereby a Denial of Service (DoS). If a BGP update message is received over an established BGP session where a BGP SR-TE policy tunnel attribute is malformed and BGP update tracing flag is enabled, the rpd will core. This issue can happen with any BGP session as long as the previous conditions are met. This issue can not propagate as the crash occurs as soon as the malformed update is received. This issue affects Juniper Networks Junos OS: 20.4 versions prior to 20.4R3-S1; 21.1 versions prior to 21.1R2-S2, 21.1R3. This issue does not affect Juniper Networks Junos OS versions prior to 20.4R1.

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 improper input validation vulnerability in the Juniper Junos OS routing protocol daemon (rpd) allows an unauthenticated attacker on the network to crash rpd by sending a malformed BGP SR-TE policy tunnel attribute in an update message over an established BGP session, but only when BGP update tracing is enabled. This causes a denial of service through rpd core dump.

MitigationApply Junos OS patches (20.4R3-S1, 21.1R2-S2, or 21.1R3 or later) to address the vulnerability. Alternatively, disable BGP update tracing as a temporary workaround if patching is not immediately feasible.

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:= 20.4= 21.1

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/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' on the device CLI to obtain the installed Junos version
    Affected if Version is 20.4 (any 20.4Rx release) or 21.1 (any 21.1Rx release)
  2. Verify if BGP update tracing is enabled
    In configuration mode, run 'show system tracing' or 'show system tracing destination' and look for BGP update tracing configuration under the routing options
    Affected if BGP update tracing is explicitly enabled - this is the required condition for the vulnerability to be exploitable
  3. Confirm BGP is configured
    Run 'show bgp summary' or 'show configuration protocols bgp' to verify BGP is configured and active
    Affected if BGP is configured and peering is established, as the attack requires sending a malformed BGP update over an established session

A system is affected only if it runs Junos 20.4 or 21.1 AND has BGP update tracing enabled, making it vulnerable to a remote denial of service via malformed BGP SR-TE policy tunnel attributes.

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

Apply Junos OS patches (20.4R3-S1, 21.1R2-S2, or 21.1R3 or later) to address the vulnerability. Alternatively, disable BGP update tracing as a temporary workaround if patching is not immediately feasible.

Recommended fix High confidence

20.4R3-S1 or later for 20.4 branch; 21.1R2-S2, 21.1R3, or later for 21.1 branch

  1. 1. Identify the current Junos OS version running on the device using 'show version'
  2. 2. Check if BGP update tracing is enabled using 'show configuration protocols bgp traceoptions' - if enabled, this is a pre-condition for exploitation
  3. 3. Schedule a maintenance window for the upgrade
  4. 4. For Junos 20.4: Upgrade to 20.4R3-S1 or later
  5. 5. For Junos 21.1: Upgrade to 21.1R2-S2, 21.1R3, or later
  6. 6. After upgrade, verify the fix by confirming the new version is running: show version
  7. 7. Optionally, disable BGP tracing if not needed: delete protocols bgp traceoptions (this mitigates the condition but does not fix the underlying vulnerability)
Caveat Standard Junos upgrade considerations apply - review release notes for your specific version for any behavior changes or migration requirements

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

Fix this in Junos Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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