Root shell access via shared SSH key
Published Aug 4, 2025 · Updated Aug 5, 2025
Use of a default cryptographic key in RUCKUS SmartZone before 6.1.2p3 Refresh Build allows remote attackers to gain root-level shell access. A built-in root-equivalent account stores the same default RSA public and private keys in its home .ssh directory on every affected system. Possession of a key copied from any RUCKUS device permits unauthenticated SSH login and full control of the controller and managed wireless environment.
Summary
What happened
Use of a default cryptographic key in RUCKUS SmartZone before 6.1.2p3 Refresh Build allows remote attackers to gain root-level shell access. A built-in root-equivalent account stores the same default RSA public and private keys in its home .ssh directory on every affected system. Possession of a key copied from any RUCKUS device permits unauthenticated SSH login and full control of the controller and managed wireless environment.
The record
- CVE
- CVE-2025-44954
- Published
- Aug 4, 2025
- Updated
- Aug 5, 2025
- Vendor
- RUCKUS Networks
- Product
- SmartZone
- Classifications
- CWE-1394, T1021.004, T1078
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 4, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <6.1.2p3 Refresh Build
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo