CVE-2020-26879

CRITICALNuclei

commscope ruckus_vriot Use of Hard-coded Credentials

Title source: VulnCheck
STIX 2.1 vulnerability

Record summary

CVE-2020-26879 has a selected CVSS score of 9.8 (critical); EIP currently links 1 Nuclei template.

Description

Ruckus vRioT through 1.5.1.0.21 has an API backdoor that is hardcoded into validate_token.py. An unauthenticated attacker can interact with the service API by using a backdoor value as the Authorization header.

Description source: CVE List

Exploitation context

Known exploitation

VulnCheck KEV
Listed · Jun 28, 2022 · VulnCheck
Reported exploitation
Observed · VulnCheck

Available material

Nuclei templates
1

Affected products and versions

1
ProductSourceVersion range

ruckus_vriot

Browse commscope / ruckus_vriot
VulnCheckVersion data not supplied

Nuclei templates

1
ProjectDiscoveryCRITICALRuckus vRioT IoT Controller - Authentication BypassCVSS 9.8

Ruckus vRioT through 1.5.1.0.21 contains an API backdoor caused by a hardcoded token in validate_token.py,letting unauthenticated attackers interact with the API without authentication.

Impact

Unauthenticated attackers can interact with the API without authentication via a hardcoded token, allowing complete control over the IoT controller and connected devices.

Remediation

Update to Ruckus vRioT version 1.5.1.0.22 or later.

WeaknessesCWE-798
AuthorsDhiyaneshDk
Template tagscvecve2020ruckusvriotiotapibackdoorauth-bypassvkevvuln
CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CPE: cpe:2.3:a:commscope:ruckus_vriot:*:*:*:*:*:*:*:*
Shodan: html:"RIoT Controller"
https://adepts.of0x.cc/ruckus-vriot-rce/ https://adepts.of0x.cc/ https://twitter.com/TheXC3LL https://x-c3ll.github.io/ https://github.com/alphaSeclab/sec-daily-2020 https://nvd.nist.gov/vuln/detail/CVE-2020-26879

Source: ProjectDiscovery

References

7