Ruckus vRIoT IoT Controller < 3.0.0.0 Hardcoded SSH Credentials RCE
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| RUCKUS Networks | vRIoT IOT Controller | unaffected |
|
No data.
No data.
No data available yet.
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.397% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Aviatrix
Aviatrix controller |
|
| CPEs | cpe:2.3:a:aviatrix:controller:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Aviatrix
Aviatrix controller |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The Ruckus vRIoT IoT Controller firmware versions prior to 3.0.0.0 (GA) contain hardcoded credentials for an operating system user account within an initialization script. The SSH service is network-accessible without IP-based restrictions. Although the configuration disables SCP and pseudo-TTY allocation, an attacker can authenticate using the hardcoded credentials and establish SSH local port forwarding to access the Docker socket. By mounting the host filesystem via Docker, an attacker can escape the container and execute arbitrary OS commands as root on the underlying vRIoT controller, resulting in complete system compromise. | |
| Title | Ruckus vRIoT IoT Controller < 3.0.0.0 Hardcoded SSH Credentials RCE | |
| Weaknesses | CWE-732 CWE-798 |
|
| References |
| |
| Metrics |
cvssV4_0
|