CVE-2017-6229
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 · uneditedRuckus Networks Unleashed AP firmware releases before 200.6.10.1.x and Ruckus Networks Zone Director firmware releases 10.1.0.0.x, 9.10.2.0.x, 9.12.3.0.x, 9.13.3.0.x, 10.0.1.0.x or before contain authenticated Root Command Injection in the CLI that could allow authenticated valid users to execute privileged commands on the respective systems.
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 confidenceAuthenticated command injection vulnerability in the CLI of Ruckus Unleashed AP and Zone Director firmware allows authenticated users to execute arbitrary root-level commands due to improper input sanitization in the command-line interface.
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.6.10.1.0< 200.6.10.1.0< 200.6.10.1.0< 200.6.10.1.0< 200.6.10.1.0< 200.6.10.1.0< 200.6.10.1.0< 200.6.10.1.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify device modelCheck the Ruckus access point or Zone Director model number via web UI, CLI, or physical label. Affected models are: R500, R600, R310, H320, H510, R710, R720, T300, and Zone Director controllers.Affected if Device is one of the listed models and firmware version is below 200.6.10.1.0
-
Check firmware versionAccess the CLI or web UI and retrieve the firmware version. In CLI, this is typically shown at login or via 'show version' or 'get version' command. In web UI, check the controller status or system info page.Affected if Firmware version is less than 200.6.10.1.0 for Unleashed AP, or falls below the patched versions (10.1.0.0.x, 9.10.2.0.x, 9.12.3.0.x, 9.13.3.0.x, 10.0.1.0.x) for Zone Director
-
Verify CLI access is enabledCheck if the CLI service is active. In the web UI, navigate to Configure > CLI or Administration > CLI Settings. Alternatively, check if SSH or telnet access to the device is permitted.Affected if CLI access is enabled and reachable (SSH/telnet port open)
-
Confirm administrative accounts existReview the list of configured administrative users who have CLI access. Check Configure > Administrators or similar in the web UI, or use 'show admin' or 'show run' in CLI.Affected if Any authenticated administrative user account exists on the device
The environment is affected if the device is one of the listed models, runs firmware version below 200.6.10.1.0 (or below patched Zone Director versions), and has CLI access enabled with at least one administrative account configured.
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 data200.6.10.1.0
Upgrade Unleashed AP firmware to 200.6.10.1.x or later, and Zone Director to patched versions beyond 10.1.0.0.x, 9.10.2.0.x, 9.12.3.0.x, 9.13.3.0.x, 10.0.1.0.x. Limit CLI access to trusted administrative users until patching is complete.
- 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-2017-6229 — 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-2017-6229 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