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
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).
- Published
- Jan 20, 2023
- Updated
- Jun 16, 2026
- EPSS
- 0.5% · 40th percentile
- CWE
- CWE-1272
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
| Vendor | Product | CPE |
|---|---|---|
| ruckuswireless | r310 firmware | cpe:2.3:o:ruckuswireless:r310_firmware |
| ruckuswireless | r310 | cpe:2.3:h:ruckuswireless:r310 |
| ruckuswireless | r500 firmware | cpe:2.3:o:ruckuswireless:r500_firmware |
| ruckuswireless | r500 | cpe:2.3:h:ruckuswireless:r500 |
| ruckuswireless | r600 firmware | cpe:2.3:o:ruckuswireless:r600_firmware |
| ruckuswireless | r600 | cpe:2.3:h:ruckuswireless:r600 |
| ruckuswireless | t300 firmware | cpe:2.3:o:ruckuswireless:t300_firmware |
| ruckuswireless | t300 | cpe:2.3:h:ruckuswireless:t300 |
| ruckuswireless | t301n firmware | cpe:2.3:o:ruckuswireless:t301n_firmware |
| ruckuswireless | t301n | cpe:2.3:h:ruckuswireless:t301n |
| ruckuswireless | t301s firmware | cpe:2.3:o:ruckuswireless:t301s_firmware |
| ruckuswireless | t301s | cpe:2.3:h:ruckuswireless:t301s |
and 16 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- ruckuswireless r310 firmware10.5.1.0.199
- ruckuswireless r500 firmware10.5.1.0.199
- ruckuswireless r600 firmware10.5.1.0.199
- ruckuswireless scg200 firmwarebefore 3.6.2.0.795
- ruckuswireless sz-100 firmwarebefore 3.6.2.0.795
- ruckuswireless sz-300 firmwarebefore 3.6.2.0.795
- ruckuswireless t300 firmware10.5.1.0.199
- ruckuswireless t301n firmware10.5.1.0.199
- ruckuswireless t301s firmware10.5.1.0.199
- ruckuswireless vsz firmwarebefore 3.6.2.0.795
- ruckuswireless zonedirector 1100 firmware9.10.2.0.130
- ruckuswireless zonedirector 1200 firmware10.2.1.0.218
- ruckuswireless zonedirector 3000 firmware10.2.1.0.218
- ruckuswireless zonedirector 5000 firmware10.0.1.0.151
Same product
ruckuswireless: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-22658In 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, Ruckus39Monitor
- CVE-2020-22654In 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, Ruckus39Monitor
- CVE-2020-22653In 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, Ruckus39Monitor
- CVE-2020-22657In 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, Ruckus36Monitor
- CVE-2020-22662In 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, Ruckus30Monitor
- CVE-2020-22660In 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, Ruckus30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-1272 · Sensitive Information Uncleared Before Debug/Power State TransitionCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
- OS Credential DumpingT1003
- Data from Local SystemT1005
- Automated CollectionT1119
- Data from Information RepositoriesT1213
- Data from Cloud Storage ObjectT1530
- Unsecured Credentials: Private KeysT1552.004
- Credentials from Password StoresT1555
- Credentials from Password Stores:KeychainT1555.001
- Data from Configuration RepositoryT1602
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
- hdhrmi.blogspot.com/2020/03/multiple-vulnerabilities-in-ruckus.html?m=1
- support.ruckuswireless.com/security_bulletins/302
Vendor advisories and official records. Exploit/PoC links are deliberately left out.