dbcve.org
R310 FirmwareOperating system · Ruckuswireless

CVE-2020-22654

CRITICAL · 9.8 CVSS v3.1 Published 2023-01-20
Fix available
A fix is available. Upgrade to 3.6.2.0.795 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 Ruckus R310 10.5.1.0.199, Ruckus R500 10.5.1.0.199, Ruckus R600 10.5.1.0.199, Ruckus T300 10.5.1.0.199, Ruckus T301n 10.5.1.0.199, Ruckus T301s 10.5.1.0.199, SmartCell Gateway 200 (SCG200) before 3.6.2.0.795, SmartZone 100 (SZ-100) before 3.6.2.0.795, SmartZone 300 (SZ300) before 3.6.2.0.795, Virtual SmartZone (vSZ) before 3.6.2.0.795, ZoneDirector 1100 9.10.2.0.130, ZoneDirector 1200 10.2.1.0.218, ZoneDirector 3000 10.2.1.0.218, ZoneDirector 5000 10.0.1.0.151, a vulnerability allows attackers to bypass firmware image bad md5 checksum failed error.

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

A detailed technical summary for this CVE is being prepared.

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
R310 FirmwareOperating system
Affected:= 10.5.1.0.199
R500 FirmwareOperating system
Affected:= 10.5.1.0.199
R600 FirmwareOperating system
Affected:= 10.5.1.0.199
T300 FirmwareOperating system
Affected:= 10.5.1.0.199
T301n FirmwareOperating system
Affected:= 10.5.1.0.199
T301s FirmwareOperating system
Affected:= 10.5.1.0.199
Scg200 FirmwareOperating system
Affected:< 3.6.2.0.795
Sz 100 FirmwareOperating system
Affected:< 3.6.2.0.795

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 3.6.2.0.795 or later
Fixed in 3.6.2.0.795
Vendor patch support.ruckuswireless.com →
Recommended fix High confidence

Upgrade to firmware version 3.6.2.0.795 or later for SmartCell Gateway 200 and SmartZone 100; upgrade to vendor-specified fixed versions for ZoneDirector models as listed in the security bulletin

  1. Identify the specific Ruckus device model (R310, R500, R600, T300, T301n, T301s, SCG200, SZ-100, or ZoneDirector) from the affected list
  2. Access the device web interface or CLI console
  3. Navigate to the firmware upgrade or system maintenance section
  4. Obtain the appropriate fixed firmware from the vendor security bulletin at https://support.ruckuswireless.com/security_bulletins/302
  5. Upload and install the fixed firmware version (3.6.2.0.795 or later for SCG200/SZ-100; newer versions for R310/R500/R600/T300/T301n/T301s; 9.10.2.0.130 or later for ZD1100; 10.2.1.0.218 or later for ZD1200/ZD3000; 10.0.1.0.151 or later for ZD5000)
  6. Verify the firmware upgrade was successful and the device is functioning normally
  7. Change administrative credentials as a best practice following any security-related firmware update
Caveat Review vendor release notes for any configuration or feature changes between versions before upgrading

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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