# CVE-2020-22656: Security feature bypass in n/a

> Attackers can force Ruckus wireless devices into a failed Secure Boot state, bypassing boot integrity checks.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jan 2023
- **Updated:** 3 Apr 2025
- **Also known as:** GHSA-gp9q-v6ph-4fp7

## What is CVE-2020-22656?

CVE-2020-22656 is a high-severity vulnerability in n/a, published on 20 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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 make the Secure Boot in failed attempts state (rfwd).

Weakness: CWE-1272 (Sensitive Information Uncleared Before Debug/Power State Transition)

## Which versions are affected by CVE-2020-22656?

It affects 14 products.


Products: Ruckuswireless R310 Firmware, Ruckuswireless R500 Firmware, Ruckuswireless R600 Firmware, Ruckuswireless Scg200 Firmware, Ruckuswireless Sz-100 Firmware, Ruckuswireless Sz-300 Firmware, Ruckuswireless T300 Firmware, Ruckuswireless T301n Firmware, Ruckuswireless T301s Firmware, Ruckuswireless Vsz Firmware, Ruckuswireless Zonedirector 1100 Firmware, Ruckuswireless Zonedirector 1200 Firmware, Ruckuswireless Zonedirector 3000 Firmware, Ruckuswireless Zonedirector 5000 Firmware.

## How do I fix CVE-2020-22656?

No fix has been published for CVE-2020-22656 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-22656 being exploited?

There is no known exploitation of CVE-2020-22656 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2020-22653](https://insights.sbomify.com/CVE-2020-22653/): Security feature bypass in n/a (critical 9.8)
- [CVE-2020-22654](https://insights.sbomify.com/CVE-2020-22654/): Security feature bypass in n/a (critical 9.8)
- [CVE-2020-22658](https://insights.sbomify.com/CVE-2020-22658/): Security feature bypass in n/a (critical 9.8)
- [CVE-2020-22657](https://insights.sbomify.com/CVE-2020-22657/): Auth bypass in n/a (critical 9.1)
- [CVE-2020-22655](https://insights.sbomify.com/CVE-2020-22655/): Missing authorization in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-22656 and fix it if it is affected.

What it is: CVE-2020-22656 is a high-severity vulnerability in n/a, published on 20 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-22656 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-22656/ (Markdown: https://insights.sbomify.com/CVE-2020-22656/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-22656
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-22656
- OSV: https://osv.dev/vulnerability/CVE-2020-22656

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-22656/
Summaries are generated and may contain mistakes; the official description above is the record.