CVE-2020-26879
published 2020-10-26CVE-2020-26879: 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…
PriorityP190critical9.8CVSS 3.1
AVNACLPRNUINSUCHIHAH
ITWEXPLOITVulnCheck KEVInitial access
Exploited in the wild
EPSS
42.48%
98.5th percentile
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.
Affected
1 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| commscope | ruckus_vriot | <= 1.5.1.0.21 | — |
Detection & IOCsextracted from sources · hover to see the quote
snort
alert http any any -> [$HTTP_SERVERS,$HOME_NET] any (msg:"ET EXPLOIT Ruckus vRIoT Authentication Bypass Attempt Inbound (CVE-2020-26879)"; flow:established,to_server; http.method; content:"POST"; http.header; header_lowercase; content:"authorization|3a 20|OlDkR|2b|oocZg|3d|"; fast_pattern; reference:url,adepts.of0x.cc/ruckus-vriot-rce/; reference:cve,2020-26879; classtype:attempted-admin; sid:2031115; rev:3; metadata:affected_product IoT, created_at 2020_10_26, cve CVE_2020_26879, deployment Perimeter, deployment Internal, confidence High, signature_severity Major, tag Description_Generated_By_Proofpoint_Nexus, updated_at 2024_11_26, mitre_tactic_id TA0001, mitre_tactic_name Initial_Access, mitre_technique_id T1190, mitre_technique_name Exploit_Public_Facing_Application; target:dest_ip;)
- →Detect exploitation attempts by matching HTTP POST requests to /service/v1/createUser with the hardcoded Authorization header value 'OlDkR+oocZg=' ↗
- →Successful exploitation returns HTTP 200 with body containing '{"ok": 1}' and '{"message":', indicating a user was created without authentication ↗
- →Use Shodan query 'html:"RIoT Controller"' to identify exposed Ruckus vRioT instances on the internet ↗
- →The Snort/ET rule triggers on the byte pattern 'authorization|3a 20|OlDkR|2b|oocZg|3d|' in HTTP headers inbound to servers (ET SID 2031115)
- ·The backdoor token is hardcoded in validate_token.py on the Ruckus vRioT device itself; the token value 'OlDkR+oocZg=' is static across all affected versions up to 1.5.1.0.21 ↗
CVSS provenance
nvdv3.19.8CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvdv2.010.0CRITICALAV:N/AC:L/Au:N/C:C/I:C/A:C
vulncheck9.8CRITICAL
CVEs like this are exactly what “Exploited This Week” covers.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-v4g7-hcw8-gwmg: Ruckus vRioT through 1
ghsa_unreviewed·2022-05-24
CVE-2020-26879 [CRITICAL] CWE-798 GHSA-v4g7-hcw8-gwmg: Ruckus vRioT through 1
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.
VulnCheck
commscope ruckus_vriot Use of Hard-coded Credentials
vulncheck·2020·CVSS 9.8
CVE-2020-26879 [CRITICAL] commscope ruckus_vriot Use of Hard-coded Credentials
commscope ruckus_vriot Use of Hard-coded Credentials
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.
Affected: commscope ruckus_vriot
Required Action: Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.
Exploitation References: https://blog.lumen.com/zuorat-hijacks-soho-routers-to-silently-stalk-networks/; https://dashboard.shadowserver.org/statistics/honeypot/vulnerability/map/?day=2025-08-11&host_type=src&vulnerability=cve-2020-26879; https://dashboard.shadowserver.org/statistics/honeypot/vulnerability/map/?day=2025-08-12&host_type=src&vu
Suricata
ET EXPLOIT Ruckus vRIoT Authentication Bypass Attempt Inbound (CVE-2020-26879)
suricata·2020-10-26·CVSS 9.8
CVE-2020-26879 [CRITICAL] ET EXPLOIT Ruckus vRIoT Authentication Bypass Attempt Inbound (CVE-2020-26879)
ET EXPLOIT Ruckus vRIoT Authentication Bypass Attempt Inbound (CVE-2020-26879)
Rule: alert http any any -> [$HTTP_SERVERS,$HOME_NET] any (msg:"ET EXPLOIT Ruckus vRIoT Authentication Bypass Attempt Inbound (CVE-2020-26879)"; flow:established,to_server; http.method; content:"POST"; http.header; header_lowercase; content:"authorization|3a 20|OlDkR|2b|oocZg|3d|"; fast_pattern; reference:url,adepts.of0x.cc/ruckus-vriot-rce/; reference:cve,2020-26879; classtype:attempted-admin; sid:2031115; rev:3; metadata:affected_product IoT, created_at 2020_10_26, cve CVE_2020_26879, deployment Perimeter, deployment Internal, confidence High, signature_severity Major, tag Description_Generated_By_Proofpoint_Nexus, updated_at 2024_11_26, mitre_tactic_id TA0001, mitre_tactic_name Initial_Access, mitre_techniqu
Nuclei
Ruckus vRioT IoT Controller - Authentication Bypass
nuclei·CVSS 9.8
CVE-2020-26879 [CRITICAL] Ruckus vRioT IoT Controller - Authentication Bypass
Ruckus vRioT IoT Controller - Authentication Bypass
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.
Template:
id: CVE-2020-26879
info:
name: Ruckus vRioT IoT Controller - Authentication Bypass
author: DhiyaneshDk
severity: critical
description: |
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 versio
No writeups or analysis indexed.
https://adepts.of0x.cchttps://adepts.of0x.cc/ruckus-vriot-rce/https://support.ruckuswireless.com/documentshttps://support.ruckuswireless.com/security_bulletins/305https://twitter.com/TheXC3LLhttps://x-c3ll.github.iohttps://adepts.of0x.cchttps://adepts.of0x.cc/ruckus-vriot-rce/https://support.ruckuswireless.com/documentshttps://support.ruckuswireless.com/security_bulletins/305https://twitter.com/TheXC3LLhttps://x-c3ll.github.io
2020-10-26
Published
Exploited in the wild