CVE-2020-13914
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 · uneditedwebs in Ruckus Wireless Unleashed through 200.7.10.102.92 allows a remote attacker to cause a denial of service (Segmentation fault) to the webserver 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 confidenceRuckus Wireless Unleashed web servers contain a vulnerability where unauthenticated remote attackers can send a crafted HTTP request causing a segmentation fault and denial of service. The vulnerability affects multiple access point models running versions prior to 200.7.10.102.92.
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<= 200.7.10.102.92CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the device web UI or CLI and confirm the device is a Ruckus Wireless Unleashed access point. This can be done via the web interface status page or by running 'show model' in the CLI.Affected if The device is not a Ruckus Unleashed access point, this CVE does not apply.
-
Determine the firmware versionIn the web UI, navigate to Administration > Firmware Upgrade or check the main status page for the current firmware version. Alternatively, run 'show version' in the CLI to retrieve the exact build number.Affected if The installed firmware version is 200.7.10.102.92 or any earlier version (versions prior to 200.7.10.102.92 are affected). Compare your version to the affected range.
-
Verify the web management interface is enabledCheck if the HTTP/HTTPS web management interface is enabled on the device. This is typically found under Administration > Management in the web UI, or via 'show http-server' in the CLI.Affected if The web server must be enabled for the vulnerability to be exploitable. If it is disabled, the attack surface may be reduced.
-
Assess network exposure of the web interfaceDetermine if the web management port (HTTP port 80 or HTTPS port 443) is reachable from untrusted networks. Check firewall rules, VLAN configuration, or perform a port scan from an external IP to confirm accessibility.Affected if The vulnerability is exploitable by unauthenticated remote attackers. If the web interface is exposed to the internet or untrusted networks, the device is at risk.
The device is affected if it is a Ruckus Unleashed access point running firmware version 200.7.10.102.92 or earlier AND has its web management interface enabled and network-accessible to unauthenticated attackers.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade affected devices to firmware version 200.7.10.102.92 or later. If immediate patching is not possible, restrict network access to the web management interface using firewall rules or VLAN isolation to prevent unauthenticated attackers from reaching the service.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-13914 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-13914 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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