HighCVE-2020-22656

    Ruckus Networks R310 Firmware: security vulnerability (CVE-2020-22656)

    Published Sources: CVE.org

    Share

    What is affected, what to do

    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).

    Update Ruckus Wireless Scg200 Firmware to version 3.6.2.0.795, Ruckus Wireless SZ-100 Firmware to version 3.6.2.0.795, Ruckus Wireless SZ-300 Firmware to version 3.6.2.0.795.

    Affected
    • Ruckus Networks R310 Firmware eq 10.5.1.0.199..10.5.1.0.199
    • Ruckus Networks R500 Firmware eq 10.5.1.0.199..10.5.1.0.199
    • Ruckus Networks R600 Firmware eq 10.5.1.0.199..10.5.1.0.199
    • Ruckus Networks T300 Firmware eq 10.5.1.0.199..10.5.1.0.199
    • Ruckus Wireless T301n Firmware eq 10.5.1.0.199..10.5.1.0.199
    • Ruckus Wireless T301s Firmware eq 10.5.1.0.199..10.5.1.0.199
    • Ruckus Wireless Scg200 Firmware lt *..3.6.2.0.795
    • Ruckus Wireless SZ-100 Firmware lt *..3.6.2.0.795
    • Ruckus Wireless SZ-300 Firmware lt *..3.6.2.0.795
    • Ruckus Wireless vSZ Firmware lt *..3.6.2.0.795
    • Ruckus Wireless Zonedirector 1100 Firmware eq 9.10.2.0.130..9.10.2.0.130
    • Ruckuswireless Zonedirector 1200 Firmware eq 10.2.1.0.218..10.2.1.0.218
    • Ruckuswireless Zonedirector 3000 Firmware eq 10.2.1.0.218..10.2.1.0.218
    • Ruckus Wireless Zonedirector 5000 Firmware eq 10.0.1.0.151..10.0.1.0.151
    Fixed in
    • Ruckus Wireless Scg200 Firmware 3.6.2.0.795
    • Ruckus Wireless SZ-100 Firmware 3.6.2.0.795
    • Ruckus Wireless SZ-300 Firmware 3.6.2.0.795
    • Ruckus Wireless vSZ Firmware 3.6.2.0.795

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    7.5

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    7.5

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: CVE.org

    0.5 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 43.3

    Show all metrics
    Severity
    High
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    54.52 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    7.5 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    7.5
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.5 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    43.3
    High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CISA assessment (SSVC)
    Exploitation: none known · automatable · Technical impact: partial
    Source: CISA Vulnrichment, as of 3 April 2025
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-1272

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    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).

    Source: NVD (NIST), cvelistv5

    Vendors and products

    Affected operating systems

    Affected operating systems
    Otherruckuswirelessr310_firmware10.5.1.0.199
    Otherruckuswirelessr500_firmware10.5.1.0.199
    Otherruckuswirelessr600_firmware10.5.1.0.199
    Otherruckuswirelessscg200_firmware—
    Otherruckuswirelesssz-100_firmware—
    Otherruckuswirelesssz-300_firmware—
    Otherruckuswirelesst300_firmware10.5.1.0.199
    Otherruckuswirelesst301n_firmware10.5.1.0.199
    Otherruckuswirelesst301s_firmware10.5.1.0.199
    Otherruckuswirelessvsz_firmware—
    Otherruckuswirelesszonedirector_1100_firmware9.10.2.0.130
    Otherruckuswirelesszonedirector_1200_firmware10.2.1.0.218
    Otherruckuswirelesszonedirector_3000_firmware10.2.1.0.218
    Otherruckuswirelesszonedirector_5000_firmware10.0.1.0.151

    Weakness classes (CWE)

    • CWE-1272Sensitive Information Uncleared Before Debug/Power State Transition

      Base

      The product performs a power or debug state transition, but it does not clear sensitive information that should no longer be accessible due to changes to information access restrictions.

      Entry at MITRE CWE-1272

    References & sources

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2020-22656
    <a href="https://intel.neosec.eu/en/cve/CVE-2020-22656"><img src="https://intel.neosec.eu/badge/cve/CVE-2020-22656.svg?lang=en" alt="CVE-2020-22656 – NEOSEC Intel" height="20"></a>