CVE-2020-26879
Last modified
CVE-2020-26879 is a critical-severity vulnerability rated 9.8/10 on the CVSS scale. 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.. EPSS estimates a 42.48% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Commscope | Ruckus Vriot | <= 1.5.1.0.21 |
References
- https://adepts.of0x.ccThird Party Advisory
- https://adepts.of0x.cc/ruckus-vriot-rce/Exploit, Third Party Advisory
- https://support.ruckuswireless.com/documentsVendor Advisory
- https://support.ruckuswireless.com/security_bulletins/305Product, Vendor Advisory
- https://twitter.com/TheXC3LLThird Party Advisory
- https://x-c3ll.github.ioThird Party Advisory
- https://adepts.of0x.ccThird Party Advisory
- https://adepts.of0x.cc/ruckus-vriot-rce/Exploit, Third Party Advisory
- https://support.ruckuswireless.com/documentsVendor Advisory
- https://support.ruckuswireless.com/security_bulletins/305Product, Vendor Advisory
- https://twitter.com/TheXC3LLThird Party Advisory
- https://x-c3ll.github.ioThird Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2020-26879?
How severe is CVE-2020-26879?
How do I fix CVE-2020-26879?
Are you affected by CVE-2020-26879?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
