CVE-2025-46117

9.1 CRITICAL

📋 TL;DR

This vulnerability allows authenticated attackers to execute arbitrary commands as root on Ruckus wireless controllers by exploiting improper input sanitization in a hidden debug script. Affected systems include CommScope Ruckus Unleashed and ZoneDirector products. Attackers need authenticated access to the restricted CLI to trigger the vulnerability.

💻 Affected Systems

Products:
  • CommScope Ruckus Unleashed
  • Ruckus ZoneDirector
Versions: Ruckus Unleashed prior to 200.15.6.212.14 and 200.17.7.0.139; ZoneDirector prior to 10.5.1.0.279
Operating Systems: Embedded Linux
Default Config Vulnerable: ⚠️ Yes
Notes: Requires authenticated access to the restricted CLI interface where the hidden debug script can be invoked.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system compromise with root-level command execution, allowing attackers to install persistent backdoors, steal sensitive data, pivot to other network segments, or render the controller inoperable.

🟠

Likely Case

Privilege escalation from authenticated user to root, enabling attackers to modify network configurations, intercept wireless traffic, or disrupt wireless services.

🟢

If Mitigated

Limited impact if proper network segmentation, access controls, and monitoring prevent attackers from reaching the vulnerable interface.

🌐 Internet-Facing: MEDIUM
🏢 Internal Only: HIGH

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires authenticated access but is straightforward once access is obtained. The vulnerability details and exploitation methods are publicly documented.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Ruckus Unleashed 200.15.6.212.14, 200.17.7.0.139 or later; ZoneDirector 10.5.1.0.279 or later

Vendor Advisory: https://support.ruckuswireless.com/security_bulletins/330

Restart Required: Yes

Instructions:

1. Download the latest firmware from Ruckus support portal. 2. Backup current configuration. 3. Apply firmware update through web interface or CLI. 4. Reboot the controller. 5. Verify the update was successful.

🔧 Temporary Workarounds

Restrict CLI Access

all

Limit access to the restricted CLI interface to only trusted administrators using network access controls and strong authentication.

Network Segmentation

all

Isolate wireless controllers in a dedicated management VLAN with strict firewall rules preventing unauthorized access.

🧯 If You Can't Patch

  • Implement strict access controls to limit who can authenticate to the controller's CLI interface
  • Monitor for unusual CLI activity and command execution patterns

🔍 How to Verify

Check if Vulnerable:

Check the controller firmware version via web interface (System > About) or CLI (show version). Compare against affected versions.

Check Version:

show version

Verify Fix Applied:

Confirm firmware version is equal to or higher than the patched versions listed in the fix section.

📡 Detection & Monitoring

Log Indicators:

  • Unusual CLI access patterns
  • Execution of .ap_debug.sh script
  • Commands executed with root privileges from non-admin accounts

Network Indicators:

  • Unexpected connections to controller management interfaces
  • Traffic patterns suggesting command execution

SIEM Query:

source="ruckus-controller" AND (event="cli_access" OR command="ap_debug")

🔗 References

📤 Share & Export