CVE-2017-6223
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 Wireless Zone Director Controller firmware releases ZD9.9.x, ZD9.10.x, ZD9.13.0.x less than 9.13.0.0.232 contain OS Command Injection vulnerabilities in the ping functionality that could allow local authenticated users to execute arbitrary privileged commands on the underlying operating system.
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 confidenceOS command injection vulnerability in the ping functionality of Ruckus Wireless Zone Director Controller firmware (ZD9.9.x, ZD9.10.x, ZD9.13.0.x prior to 9.13.0.0.232) allows authenticated local users to execute arbitrary privileged commands on the underlying operating system.
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= zd9.9.0.0.205= zd9.9.0.0.212= zd9.9.0.0.216= zd9.10.0.0.218= zd9.13.0.0.103= zd9.13.0.0.209CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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.
-
Check Zone Director firmware versionAccess the Zone Director web interface and navigate to Administration > Backup & Restore or check the login page footer for the firmware version. Alternatively, use the CLI command 'show version' if you have SSH access.Affected if The installed version matches one of the affected versions: zd9.9.0.0.205, zd9.9.0.0.212, zd9.9.0.0.216, zd9.10.0.0.218, zd9.13.0.0.103, or zd9.13.0.0.209, or is any version prior to 9.13.0.0.232.
-
Verify ping functionality is accessibleLocate the ping or diagnostic tool in the Zone Director web interface, typically under Maintenance > Diagnostics or a similar troubleshooting section. Confirm the ping feature exists and is accessible to authenticated users.Affected if The ping feature is present and available to authenticated administrative users.
-
Confirm administrative access levelLog into the Zone Director with an administrator account. Verify you have authenticated access to the device with privileges to access the ping/diagnostic functionality.Affected if You have valid administrator credentials that grant authenticated access to the Zone Director.
If the installed firmware version is any of the affected versions listed (zd9.9.0.0.205 through zd9.13.0.0.209) or is earlier than 9.13.0.0.232, and you have authenticated administrative access to the ping feature, your environment is affected by CVE-2017-6223.
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 dataUpdate Zone Director firmware to version 9.13.0.0.232 or later to remediate the command injection vulnerability. Restrict administrative access to trusted users until the patch is applied.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-6223 — 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-6223 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