LiveActive security incident?Get immediate response
CVE Record

CVE-2020-22655: 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,...

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 persistently to writing unauthorized image.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This flaw affects several Ruckus access points and controller platforms. A remote unauthenticated attacker could make a persistent unauthorized image write, creating an integrity risk on network infrastructure. The sources do not show active exploitation, but the issue is high severity because it requires no login or user interaction.

Executive priority

Treat this as a high-priority network infrastructure hygiene issue. Prioritize internet-reachable or broadly reachable management planes first, then complete firmware validation across remaining Ruckus estates.

Technical view

CVE-2020-22655 is a CWE-284 improper access-control issue. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N, meaning network-reachable, low-complexity, unauthenticated exploitation with high integrity impact and no stated confidentiality or availability impact.

Likely exposure

Exposure is most likely in organizations still running the listed Ruckus R310, R500, R600, T300, T301n, T301s, SCG200, SmartZone, vSZ, or ZoneDirector versions on reachable management or device interfaces.

Exploitation context

The provided bundle marks KEV as false and does not cite active exploitation. Public references include a Ruckus security bulletin and a researcher blog, so defenders should assume the vulnerability details are publicly known.

Researcher notes

The affected-product data in the bundle is inconsistent: the structured affected field is n/a, while the description lists specific models and versions. Base validation on the description and vendor bulletin, and avoid assuming fixes beyond stated version boundaries.

Mitigation direction

  • Inventory all listed Ruckus access point and controller models.
  • Upgrade SCG200, SZ-100, SZ300, and vSZ to at least 3.6.2.0.795.
  • Check the Ruckus bulletin for fixed releases for AP and ZoneDirector versions.
  • Restrict management interfaces to trusted administrative networks only.
  • Monitor vendor guidance for model-specific remediation details.

Validation and detection

  • Confirm exact model and firmware version for every Ruckus device.
  • Compare findings against the CVE description and Ruckus bulletin.
  • Verify management interfaces are not exposed to untrusted networks.
  • Review device logs for unexpected image or firmware write activity.
  • Document exceptions where vendor-fixed firmware is unavailable or unconfirmed.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-284: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-22655 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2020-22655Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-284 · source CWE mapping

Improper Access Control

Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.