CVE-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 using a backdoor value as the Authorization header.
References
Link Resource
https://adepts.of0x.cc Third Party Advisory
https://adepts.of0x.cc/ruckus-vriot-rce/ Exploit Third Party Advisory
https://support.ruckuswireless.com/documents Vendor Advisory
https://support.ruckuswireless.com/security_bulletins/305 Product Vendor Advisory
https://twitter.com/TheXC3LL Third Party Advisory
https://x-c3ll.github.io Third Party Advisory
Configurations

Configuration 1 (hide)

AND
cpe:2.3:a:commscope:ruckus_vriot:*:*:*:*:*:*:*:*
cpe:2.3:h:commscope:ruckus_iot_module:-:*:*:*:*:*:*:*

History

No history.

Information

Published : 2020-10-26 20:15

Updated : 2024-02-28 18:08


NVD link : CVE-2020-26879

Mitre link : CVE-2020-26879

CVE.ORG link : CVE-2020-26879


JSON object : View

Products Affected

commscope

  • ruckus_vriot
  • ruckus_iot_module
CWE
CWE-798

Use of Hard-coded Credentials