dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 2 Jun 2023.
Ruckus Wireless AdminApplication · Ruckuswireless

CVE-2023-25717

CRITICAL · 9.8 CVSS v3.1 Published 2023-02-13
Fix available
A fix is available. Upgrade to 3.6.2.0.795 / 5.2.1.3 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges Zero-click Patch available

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 · unedited
Ruckus Wireless Admin through 10.4 allows Remote Code Execution via an unauthenticated HTTP GET Request, as demonstrated by a /forms/doLogin?login_username=admin&password=password$(curl substring.

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 confidence

Ruckus Wireless Admin through version 10.4 contains a command injection vulnerability in the /forms/doLogin endpoint. An unauthenticated attacker can inject arbitrary shell commands via the password parameter using command substitution syntax (e.g., $(command)), leading to full system compromise.

MitigationImmediately restrict external network access to the admin interface via firewall or ACLs. Apply vendor security patches when available; if no patch exists, consider disabling the web admin interface or upgrading to an unaffected version.

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
Ruckus Wireless AdminApplication
Affected:<= 10.4
Smartzone ApOperating system
Affected:< 6.1.0.0.9240< 5.2.2.0.2064< 3.6.2.0.795< 6.1.1.0.1274
Ruckus Smartzone FirmwareOperating system
Affected:< 5.2.1.3= 6.1.0.0.935< 5.2.1.3.1695

CVSS 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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Ruckus product and model
    Access the web UI login page or use CLI (show version) to confirm the device is Ruckus Wireless Admin or Smartzone AP. Look for product name in the UI footer or system info.
    Affected if The product is Ruckus Wireless Admin or Ruckus Smartzone AP/Smartzone Controller.
  2. Determine the installed firmware version
    In the web UI, go to Administration > System > Firmware or check the login page footer for version number. Via CLI, use 'show version' or 'get version'.
    Affected if Version is 10.4 or lower for Wireless Admin, or matches the vulnerable Smartzone ranges: < 6.1.0.0.9240, < 5.2.2.0.2064, < 3.6.2.0.795, < 6.1.1.0.1274, < 5.2.1.3, or = 6.1.0.0.935.
  3. Verify the web management interface is reachable
    Attempt to access the /forms/doLogin endpoint via HTTP/HTTPS from an authorized network location: curl -k https://<device-ip>/forms/doLogin
    Affected if The endpoint responds with a login form or accepts POST requests.
  4. Confirm the management interface is network-accessible
    Check firewall rules or network ACLs to determine if the management web interface (port 443/8443) is accessible from untrusted networks. Use 'show running-config' on the firewall or review access lists.
    Affected if The management interface is exposed to untrusted networks or the internet.

You are affected if the device runs Ruckus Wireless Admin <= 10.4 or a Smartzone version in the vulnerable ranges AND the web management interface is network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 3.6.2.0.795 / 5.2.1.3 / 5.2.1.3.1695 or later
Fixed in 3.6.2.0.7955.2.1.35.2.1.3.1695
Vendor patch support.ruckuswireless.com →
Interim mitigation

Immediately restrict external network access to the admin interface via firewall or ACLs. Apply vendor security patches when available; if no patch exists, consider disabling the web admin interface or upgrading to an unaffected version.

Recommended fix High confidence

Ruckus Wireless Admin: 10.4.1 or later; Smartzone AP: 6.1.0.0.9240 or later / 5.2.2.0.2064 or later / 3.6.2.0.795 or later / 6.1.1.0.1274 or later; Smartzone Firmware: 5.2.1.3.1695 or later (avoid 6.1.0.0.935)

  1. Identify the specific Ruckus product model and current firmware version using the web GUI or CLI command 'show version'
  2. Determine the appropriate upgrade path based on your current version and product type (Wireless Admin, Smartzone AP, or Smartzone Firmware)
  3. Download the fixed firmware from the official Ruckus Support portal at support.ruckuswireless.com
  4. Back up the current configuration before upgrading
  5. Upload the firmware through the web interface (System > Upgrade) or via CLI using 'upgrade' command
  6. Verify the upgrade was successful by checking the new version number and testing core functionality
Caveat Review release notes for any configuration changes or features deprecated in the target version; some upgrades may require intermediate steps if jumping multiple major versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ruckus Wireless Admin Exploited in the wild — priority engagement
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,840
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,144.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-25717 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-25717 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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