dbcve.org
JunosOperating system · Juniper

CVE-2022-22154

MEDIUM · 6.8 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 →
73/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
In a Junos Fusion scenario an External Control of Critical State Data vulnerability in the Satellite Device (SD) control state machine of Juniper Networks Junos OS allows an attacker who is able to make physical changes to the cabling of the device to cause a denial of service (DoS). An SD can get rebooted and subsequently controlled by an Aggregation Device (AD) which does not belong to the original Fusion setup and is just connected to an extended port of the SD. To carry out this attack the attacker needs to have physical access to the cabling between the SD and the original AD. This issue affects: Juniper Networks Junos OS 16.1R1 and later versions prior to 18.4R3-S10; 19.1 versions prior to 19.1R3-S7; 19.2 versions prior to 19.2R3-S4. This issue does not affect Juniper Networks Junos OS versions prior to 16.1R1.

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

In Junos Fusion deployments, a vulnerability exists in the Satellite Device (SD) control state machine where an SD can be rebooted and subsequently controlled by an unauthorized Aggregation Device (AD) connected to an extended port. An attacker with physical access to the cabling between the SD and original AD can cause the SD to reboot and be taken over by a rogue AD, resulting in denial of service.

MitigationUpgrade Junos OS to the fixed versions (18.4R3-S10 and later, 19.1R3-S7 and later, 19.2R3-S4 and later). Additionally, restrict physical access to network cabling and equipment to prevent unauthorized physical connections.

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:= 16.1= 16.1x65= 16.1x70= 16.2= 17.1= 17.2= 17.2x75= 17.3= 17.4= 18.1= 18.1x75= 18.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
Physical
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Confirm Junos Fusion deployment
    Check if the device is configured as an Aggregation Device (AD) in a Junos Fusion architecture by reviewing the system configuration for 'fabric' or 'satellite' related commands such as 'show chassis fabric topology' or 'show satellite status'
    Affected if The device is an Aggregation Device in a Junos Fusion deployment with Satellite Devices connected
  2. Verify Junos OS version
    Run the command 'show version' or 'show version detail' to obtain the installed Junos OS version number
    Affected if The installed Junos version matches one of the affected versions: 16.1, 16.1x65, 16.1x70, 16.2, 17.1, 17.2, 17.2x75, 17.3, 17.4, 18.1, 18.1x75, or 18.2
  3. Identify extended port configuration
    Run 'show chassis fabric topology' or 'show interface diagnostics' to identify if any satellite devices are connected via extended ports on the Aggregation Device
    Affected if Satellite Devices are connected to the Aggregation Device through extended ports (typically interface names ending in 'xe-' or 'et-' pointing to satellite devices)

You are affected if you are running a Junos Fusion deployment with an Aggregation Device on any of the listed affected Junos versions and have Satellite Devices connected via extended ports, where an attacker with physical access to the cabling could exploit the SD control state machine flaw.

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 Junos OS to the fixed versions (18.4R3-S10 and later, 19.1R3-S7 and later, 19.2R3-S4 and later). Additionally, restrict physical access to network cabling and equipment to prevent unauthorized physical connections.

Recommended fix High confidence

18.4R3-S10 or later (or 19.1R3-S7 / 19.2R3-S4 depending on current version branch)

  1. 1. Identify the current Junos OS version running on the device using 'show version' command
  2. 2. Determine the appropriate upgrade path based on current version: if on 16.1x or 16.2, upgrade to 18.4R3-S10 or later; if on 19.1.x, upgrade to 19.1R3-S7 or later; if on 19.2.x, upgrade to 19.2R3-S4 or later
  3. 3. Download the appropriate Junos Service Release (SBR) from the Juniper Networks support portal
  4. 4. Validate the software package checksum before installation
  5. 5. Schedule a maintenance window as upgrade requires reboot
  6. 6. Install the upgrade using 'request system software add <package>' command
  7. 7. Reboot the device after installation completes using 'request system reboot'
  8. 8. After reboot, verify the new version is running with 'show version' and confirm the fix is applied
Caveat Standard Junos upgrade risks apply - review release notes for your version branch for any compatibility concerns or configuration changes needed

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

Fix this in Junos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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