CVE-2025-46121
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 · uneditedAn issue was discovered in CommScope Ruckus Unleashed prior to 200.15.6.212.14 and 200.17.7.0.139, where the functions `stamgr_cfg_adpt_addStaFavourite` and `stamgr_cfg_adpt_addStaIot` pass a client hostname directly to snprintf as the format string. A remote attacker can exploit this flaw either by sending a crafted request to the authenticated endpoint `/admin/_conf.jsp`, or without authentication and without direct network access to the controller by spoofing the MAC address of a favourite station and embedding malicious format specifiers in the DHCP hostname field, resulting in unauthenticated format-string processing and arbitrary code execution on the controller.
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 confidenceFormat string vulnerability in Ruckus Unleashed AP controllers where client hostnames are passed directly as format strings to snprintf in stamgr_cfg_adpt_addStaFavourite and stamgr_cfg_adpt_addStaIot functions. Exploitable via authenticated HTTP requests to /admin/_conf.jsp or remotely without authentication through DHCP hostname injection via MAC address spoofing, allowing unauthenticated arbitrary code execution.
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.15.6.212.14>= 200.17, < 200.17.7.0.139< 10.5.1.0.279CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Ruckus device model and firmware versionAccess the web UI or CLI and locate the firmware version information, typically under Administration > Diagnostics > System Info or via 'show version' command in CLIAffected if The firmware version is < 200.15.6.212.14, or >= 200.17 but < 200.17.7.0.139 for Unleashed, or < 10.5.1.0.279 for Zonedirector
-
Determine if the web management interface is externally accessibleAttempt to access http(s)://<device-ip>/admin/_conf.jsp from an external network location or review firewall rules allowing HTTP/HTTPS to the controllerAffected if The /admin/_conf.jsp endpoint is reachable from an untrusted network without VPN segmentation
-
Verify DHCP service exposure on the networkIdentify if the Ruckus controller is acting as a DHCP server for client devices and whether untrusted clients can send DHCP requests to itAffected if The device is providing DHCP services to untrusted or guest network segments where MAC address spoofing is possible
-
Check for unauthenticated access to admin interfacesAttempt a request to the login page or verify whether authentication is enforced for /admin/_conf.jsp without providing credentialsAffected if The endpoint permits unauthenticated access or the authentication mechanism can be bypassed
A user is affected if their Ruckus Unleashed or Zonedirector firmware version falls within the vulnerable ranges AND the device web interface or DHCP service is accessible from an attacker's network location.
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.
dbcve · scoped10.5.1.0.279200.15.6.212.14200.17.7.0.139
Upgrade Ruckus Unleashed to version 200.15.6.212.14 or later (200.17.x branch to 200.17.7.0.139 or later) to patch the format string vulnerability. Network segmentation can limit exposure while update planning occurs.
Ruckus Unleashed: 200.15.6.212.14 or later (200.15.x branch) / 200.17.7.0.139 or later (200.17.x branch); Ruckus Zonedirector: 10.5.1.0.279 or later
- 1. Identify the currently running Ruckus Unleashed or Zonedirector firmware version via the web UI or CLI
- 2. For Ruckus Unleashed: If running version 200.15.x, upgrade to 200.15.6.212.14 or later; if running version 200.17.x, upgrade to 200.17.7.0.139 or later
- 3. For Ruckus Zonedirector: Upgrade to version 10.5.1.0.279 or later
- 4. Download the appropriate firmware from the official Ruckus support portal (support.ruckuswireless.com)
- 5. Upload and apply the firmware via the controller's web interface under Administration > Firmware Upgrade, or via CLI using the firmware upgrade command
- 6. After upgrade, verify the new firmware version is installed and the format string vulnerability is patched
- 7. Review system logs to confirm no exploitation occurred prior to patching
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46121 — 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-2025-46121 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