CVE-2020-13915
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 · uneditedInsecure permissions in emfd/libemf in Ruckus Wireless Unleashed through 200.7.10.102.92 allow a remote attacker to overwrite admin credentials 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 confidenceThe emfd/libemf component in Ruckus Wireless Unleashed firmware versions up to 200.7.10.102.92 contains insecure permissions that allow unauthenticated remote attackers to overwrite admin credentials via specially crafted HTTP requests, enabling full device compromise through authentication bypass.
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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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.
-
Check the installed firmware versionAccess the AP CLI or web UI and retrieve the firmware version. In CLI, typically use 'show version' or 'sysinfo' command. In web UI, check the dashboard or system status page.Affected if The firmware version is 200.7.10.102.92 or lower (any version up to and including 200.7.10.102.92).
-
Identify if the emfd or libemf service is presentCheck the running processes on the device for emfd or examine system logs for emfd-related entries. This component handles the embedded management framework.Affected if The emfd service is running and accessible on the device, indicating the vulnerable component is present.
-
Verify HTTP management interface accessibilityAttempt to access the device's HTTP/HTTPS management interface from an untrusted network segment. The vulnerability is exploitable via specially crafted HTTP requests to the management interface.Affected if The HTTP management interface is exposed to unauthenticated network access (not restricted by ACLs or firewall).
-
Review admin account configurationCheck the admin user accounts configured on the device through the web UI (Administration > Admin Users) or CLI ('show admin users' or similar). Look for any unexpected or unauthorized admin accounts.Affected if There are unexpected admin accounts present, or evidence of credential modification, that were not created by legitimate administrators.
The device is affected if running firmware version 200.7.10.102.92 or lower AND the HTTP management interface is accessible to unauthenticated network attackers, allowing them to overwrite admin credentials.
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 to firmware version beyond 200.7.10.102.92 if a patch is available, or restrict network access to the device management interface using firewalls/ACLs to prevent unauthenticated HTTP access.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-13915 — 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-13915 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