CVE intelligence and bounded remediation

CVE-2020-22654 — Ruckuswireless R310 Firmware security vulnerability

Critical CVSS 9.8

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.

Severity
Critical
CVSS
9.8 (3.1)
Published
2023-01-20
CISA KEV
Not currently listed
Ecosystem
operating-system
Weaknesses
CWE-494

Affected products

  • ruckuswireless / r310_firmware / 10.5.1.0.199
  • ruckuswireless / r500_firmware / 10.5.1.0.199
  • ruckuswireless / r600_firmware / 10.5.1.0.199
  • ruckuswireless / t300_firmware / 10.5.1.0.199
  • ruckuswireless / t301n_firmware / 10.5.1.0.199
  • ruckuswireless / t301s_firmware / 10.5.1.0.199

Showing 6 representative product identities from 14 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

Supply-chain, dependency, build, and update integrity

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Trace affected packages, source archives, build actions, plugins, installers, and updates from declared source to deployed artifact.
  • Confirm provenance, signatures or digests, namespace ownership, lockfile resolution, registry configuration, and build-runner trust boundaries.
  • Inventory direct, transitive, vendored, generated, and bundled copies across releases and distribution channels.

Remediate safely

  • Move to a maintained trusted artifact or remove the dependency; pin immutable identities and verify provenance and integrity before use.
  • Regenerate lockfiles and artifacts in a clean isolated build, minimize build credentials and network access, and produce an updated software bill of materials.
  • Require reviewed update policy, protected publishing, and reproducible or independently attestable builds where supported.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.