Secure Boot failure via image upgrade
Published Jan 20, 2023 · Updated Apr 3, 2025
Secure Boot failure in Ruckus WLAN firmware allows remote attackers to alter verification state through the image-upgrade path. The image-upgrade path accepts network input that can place Secure Boot into its rfwd failed-attempt state; public sources do not identify the responsible handler or validation error. No authentication or user interaction is required, and the reported consequence is alteration of boot-verification state rather than code execution or data disclosure.
Summary
What happened
Secure Boot failure in Ruckus WLAN firmware allows remote attackers to alter verification state through the image-upgrade path. The image-upgrade path accepts network input that can place Secure Boot into its rfwd failed-attempt state; public sources do not identify the responsible handler or validation error. No authentication or user interaction is required, and the reported consequence is alteration of boot-verification state rather than code execution or data disclosure.
The record
- CVE
- CVE-2020-22656
- Published
- Jan 20, 2023
- Updated
- Apr 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-1272
- 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