dbcve.org
Unleashed FirmwareOperating system · Ruckuswireless

CVE-2020-13916

CRITICAL · 9.8 CVSS v3.1 Published 2020-07-28
Fix available
A fix is available. Upgrade to after 200.7.10.102.92 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A stack buffer overflow in webs in Ruckus Wireless Unleashed through 200.7.10.102.92 allows a remote attacker to execute code via an unauthenticated crafted HTTP request. This affects C110, E510, H320, H510, M510, R320, R310, R500, R510 R600, R610, R710, R720, R750, T300, T301n, T301s, T310c, T310d, T310n, T310s, T610, T710, and T710s devices.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Stack buffer overflow vulnerability in the webs HTTP service of Ruckus Wireless Unleashed APs allows unauthenticated remote code execution via specially crafted HTTP requests. This pre-auth RCE affects the web management interface without requiring credentials.

MitigationApply vendor firmware updates beyond 200.7.10.102.92. Until patched, restrict management interface access via firewall rules or VLAN segmentation to prevent external exploitation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Unleashed FirmwareOperating system
Affected:<= 200.7.10.102.92

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify device as Ruckus Wireless Unleashed AP
    Access the device management interface or check the device model documentation to confirm it is a Ruckus Wireless Unleashed access point
    Affected if The device is not a Ruckus Wireless Unleashed AP - this vulnerability only affects that product line
  2. Check the firmware version
    Log into the web management interface and navigate to the firmware/version information page, or use the device CLI command 'show version' to retrieve the installed firmware version
    Affected if The installed firmware version is 200.7.10.102.92 or any version lower than this - these are in the affected range
  3. Verify the web HTTP service is accessible
    Attempt to access the device web management interface over HTTP (port 80) or HTTPS (port 443) from a test client - confirm the webs service responds to HTTP requests
    Affected if The webs HTTP service is exposed and accessible on the network - this is required for exploitation
  4. Confirm no network segmentation is applied
    Review network configuration to determine if the management interface is isolated on a separate VLAN or protected by firewall rules that block external access
    Affected if The management interface is directly accessible from untrusted networks without firewall restrictions - this increases exposure to the vulnerability

The environment is affected if the device is a Ruckus Wireless Unleashed AP running firmware version 200.7.10.102.92 or lower, and the web management interface (webs HTTP service) is accessible on the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 200.7.10.102.92
Interim mitigation

Apply vendor firmware updates beyond 200.7.10.102.92. Until patched, restrict management interface access via firewall rules or VLAN segmentation to prevent external exploitation.

Recommended fix Moderate confidence

Ruckus Unleashed firmware version > 200.7.10.102.92 (contact Ruckus support for exact fixed release)

  1. 1. Identify the specific Ruckus Unleashed device model from the affected list (C110, E510, H320, H510, M510, R320, R310, R500, R510, R600, R610, R710, R720, R750, T300, T301n, T301s, T310c, T310d, T310n, T310s, T610, T710, T710s)
  2. 2. Access the device web interface or CLI management console
  3. 3. Navigate to the firmware update section (typically under Administration > Firmware Upgrade or Maintenance > Upgrade)
  4. 4. Obtain the latest Ruckus Unleashed firmware release from support.ruckuswireless.com or the official Ruckus download portal
  5. 5. Upload and apply the firmware update to remediate the stack buffer overflow vulnerability
  6. 6. After upgrade, verify the firmware version is > 200.7.10.102.92 and confirm the device is functioning normally
Caveat Review Ruckus release notes for any configuration or feature changes between versions; test upgrade in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Unleashed Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-13916 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-13916 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data