Firmware rollback via Secure Boot failure bypass
Published Jan 20, 2023 · Updated Apr 3, 2025
Secure Boot bypass in RUCKUS network products allows remote attackers to run a previous backup firmware image after forced boot failures. The boot fallback path launches the prior backup image after repeated Secure Boot verification failures instead of preserving the boot trust boundary. No credentials or user interaction are required; execution is temporary and limited to the stored backup image, affecting device-operation integrity.
Summary
What happened
Secure Boot bypass in RUCKUS network products allows remote attackers to run a previous backup firmware image after forced boot failures. The boot fallback path launches the prior backup image after repeated Secure Boot verification failures instead of preserving the boot trust boundary. No credentials or user interaction are required; execution is temporary and limited to the stored backup image, affecting device-operation integrity.
The record
- CVE
- CVE-2020-22660
- Published
- Jan 20, 2023
- Updated
- Apr 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-290, T1542.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 20, 2023CVE publishedPublication date reported by the CVE source.
- Apr 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo