dbcve.org
Ruckus Smartzone FirmwareOperating system · Commscope

CVE-2025-44954

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-04
Fix available
A fix is available. Upgrade to 6.1.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 SmartZone (SZ) before 6.1.2p3 Refresh Build has a hardcoded SSH private key for a root-equivalent user account.

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 SmartZone contains a hardcoded SSH private key embedded in the software/firmware that provides root-equivalent access to the system. An attacker with knowledge of this key can remotely authenticate via SSH to any affected SmartZone deployment without requiring legitimate credentials, achieving full administrative control.

MitigationUpgrade RUCKUS SmartZone to version 6.1.2p3 Refresh Build or later. Until patched, restrict SSH access to trusted management networks only via firewall rules or access control lists.

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 Smartzone FirmwareOperating system
Affected:< 6.1.2= 6.1.2= 7.0.0= 7.1.0

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. Determine the installed SmartZone firmware version
    Log into the SmartZone controller web interface and navigate to Administration > System > Firmware or use the CLI command 'show version' via console/SSH. Alternatively, check the boot screen or system information page.
    Affected if The installed version is < 6.1.2, = 6.1.2, = 7.0.0, or = 7.1.0
  2. Confirm SSH service is enabled on the SmartZone appliance
    Access the SmartZone admin interface and go to Configuration > Network > Services or use the CLI to check SSH service status. Verify whether SSH (port 22) is listed as enabled and listening.
    Affected if SSH service is enabled and accessible on the management interface
  3. Verify SSH access is not restricted to trusted networks
    Check the firewall rules, access control lists, or network segmentation settings that govern SSH access to the SmartZone management IP. Confirm whether port 22 is open to untrusted or public networks.
    Affected if SSH port 22 is reachable from networks outside trusted management IP ranges

You are affected if your SmartZone firmware version falls within the vulnerable ranges AND SSH is enabled and accessible, allowing an attacker with knowledge of the hardcoded key to authenticate without credentials.

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 6.1.2 or later
Fixed in 6.1.2
Interim mitigation

Upgrade RUCKUS SmartZone to version 6.1.2p3 Refresh Build or later. Until patched, restrict SSH access to trusted management networks only via firewall rules or access control lists.

Recommended fix High confidence

6.1.2p3 Refresh Build (or later, e.g., 7.0.1/7.1.1)

  1. Log into the SmartZone web UI as an administrator.
  2. Navigate to Administration > Firmware and note the current running version.
  3. Download the fixed firmware image (e.g., SZ-6.1.2p3-Release.pkg) from the official CommScope (Ruckus) support portal.
  4. Back up the current configuration (System > Backup & Restore).
  5. In the Firmware page, click Upload New Firmware and select the downloaded file.
  6. After upload, go to Cluster Management, select the controllers, and schedule an upgrade to the new image.
  7. Allow the controllers to reboot and apply the firmware; confirm the upgrade completes without errors.
  8. Log back into the UI, verify the version under Dashboard > System Information shows 6.1.2p3 (or later).
Caveat Upgrade may cause brief downtime and may require AP re-provisioning; back up configuration before proceeding.

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

Fix this in Ruckus Smartzone Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-44954 — 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-2025-44954 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