CVE-2020-26879
First published: Mon Oct 26 2020(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Commscope Ruckus Vriot | <=1.5.1.0.21 | |
| Commscope Ruckus Iot Module |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is CVE-2020-26879?
CVE-2020-26879 is a vulnerability in Ruckus vRioT through 1.5.1.0.21 that allows unauthenticated attackers to interact with the service API using a backdoor value as the Authorization header.
How severe is CVE-2020-26879?
CVE-2020-26879 has a severity rating of 9.8 (Critical).
How can an attacker exploit CVE-2020-26879?
An attacker can exploit CVE-2020-26879 by sending requests to the service API with a backdoor value as the Authorization header.
What is the affected software for CVE-2020-26879?
The affected software for CVE-2020-26879 is Ruckus vRioT version 1.5.1.0.21.
Is Commscope Ruckus Iot Module affected by CVE-2020-26879?
No, Commscope Ruckus Iot Module is not affected by CVE-2020-26879.
- collector/nvd-index
- agent/weakness
- agent/references
- agent/type
- agent/event
- agent/severity
- agent/author
- agent/description
- agent/softwarecombine
- agent/first-publish-date
- agent/last-modified-date
- agent/tags
- collector/mitre-cve
- source/MITRE
- vendor/commscope
- canonical/commscope ruckus vriot
- version/commscope ruckus vriot/1.5.1.0.21
- canonical/commscope ruckus iot module