CVE-2020-26879

high-risk
Published 2020-10-26

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.

Do I need to act?

!
89.5% chance of exploitation in next 30 days
EPSS score — higher than 11% of all CVEs
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
9
CVSS 9.8/10 Critical
NETWORK / LOW complexity

Affected Products (1)

Affected Vendors

Commscope

References (12)

Third Party Advisory https://adepts.of0x.cc
Exploit https://adepts.of0x.cc/ruckus-vriot-rce/
Vendor Advisory https://support.ruckuswireless.com/documents
Product https://support.ruckuswireless.com/security_bulletins/305
Third Party Advisory https://twitter.com/TheXC3LL
Third Party Advisory https://x-c3ll.github.io
Third Party Advisory https://adepts.of0x.cc
Exploit https://adepts.of0x.cc/ruckus-vriot-rce/
Vendor Advisory https://support.ruckuswireless.com/documents
Product https://support.ruckuswireless.com/security_bulletins/305
Third Party Advisory https://twitter.com/TheXC3LL
Third Party Advisory https://x-c3ll.github.io
57
/ 100
high-risk
Severity 32/34 · Critical
Exploitability 20/34 · Moderate
Exposure 5/34 · Minimal