CVE-2020-13917
Summary
| CVE | CVE-2020-13917 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2020-07-28 15:15:00 UTC |
| Updated | 2021-07-21 11:39:00 UTC |
| Description | rkscli in Ruckus Wireless Unleashed through 200.7.10.92 allows a remote attacker to achieve command injection and jailbreak the CLI via a crafted CLI command. This affects C110, E510, H320, H510, M510, R320, R310, R500, R510 R600, R610, R710, R720, R750, T300, T301n, T301s, T310c, T310d, T310n, T310s, T610, T710, and T710s devices. |
Risk And Classification
Problem Types: CWE-77
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Hardware | Ruckuswireless | C110 | - | All | All | All |
| Hardware | Ruckuswireless | C110 | - | All | All | All |
| Hardware | Ruckuswireless | E510 | - | All | All | All |
| Hardware | Ruckuswireless | E510 | - | All | All | All |
| Hardware | Ruckuswireless | H320 | - | All | All | All |
| Hardware | Ruckuswireless | H320 | - | All | All | All |
| Hardware | Ruckuswireless | H510 | - | All | All | All |
| Hardware | Ruckuswireless | H510 | - | All | All | All |
| Hardware | Ruckuswireless | M510 | - | All | All | All |
| Hardware | Ruckuswireless | M510 | - | All | All | All |
| Hardware | Ruckuswireless | R310 | - | All | All | All |
| Hardware | Ruckuswireless | R310 | - | All | All | All |
| Hardware | Ruckuswireless | R320 | - | All | All | All |
| Hardware | Ruckuswireless | R320 | - | All | All | All |
| Hardware | Ruckuswireless | R500 | - | All | All | All |
| Hardware | Ruckuswireless | R500 | - | All | All | All |
| Hardware | Ruckuswireless | R510 | - | All | All | All |
| Hardware | Ruckuswireless | R510 | - | All | All | All |
| Hardware | Ruckuswireless | R600 | - | All | All | All |
| Hardware | Ruckuswireless | R600 | - | All | All | All |
| Hardware | Ruckuswireless | R610 | - | All | All | All |
| Hardware | Ruckuswireless | R610 | - | All | All | All |
| Hardware | Ruckuswireless | R710 | - | All | All | All |
| Hardware | Ruckuswireless | R710 | - | All | All | All |
| Hardware | Ruckuswireless | R720 | - | All | All | All |
| Hardware | Ruckuswireless | R720 | - | All | All | All |
| Hardware | Ruckuswireless | R750 | - | All | All | All |
| Hardware | Ruckuswireless | R750 | - | All | All | All |
| Hardware | Ruckuswireless | T300 | - | All | All | All |
| Hardware | Ruckuswireless | T300 | - | All | All | All |
| Hardware | Ruckuswireless | T301n | - | All | All | All |
| Hardware | Ruckuswireless | T301n | - | All | All | All |
| Hardware | Ruckuswireless | T301s | - | All | All | All |
| Hardware | Ruckuswireless | T301s | - | All | All | All |
| Hardware | Ruckuswireless | T310c | - | All | All | All |
| Hardware | Ruckuswireless | T310c | - | All | All | All |
| Hardware | Ruckuswireless | T310d | - | All | All | All |
| Hardware | Ruckuswireless | T310d | - | All | All | All |
| Hardware | Ruckuswireless | T310n | - | All | All | All |
| Hardware | Ruckuswireless | T310n | - | All | All | All |
| Hardware | Ruckuswireless | T310s | - | All | All | All |
| Hardware | Ruckuswireless | T310s | - | All | All | All |
| Hardware | Ruckuswireless | T610 | - | All | All | All |
| Hardware | Ruckuswireless | T610 | - | All | All | All |
| Hardware | Ruckuswireless | T710 | - | All | All | All |
| Hardware | Ruckuswireless | T710 | - | All | All | All |
| Hardware | Ruckuswireless | T710s | - | All | All | All |
| Hardware | Ruckuswireless | T710s | - | All | All | All |
| Operating System | Ruckuswireless | Unleashed Firmware | All | All | All | All |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| 20200615 | Security Bulletins | Ruckus Wireless Support | CONFIRM | support.ruckuswireless.com | Vendor Advisory |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.