Ruckus Wireless C110 up to 200.7.10.92 rkscli os command injection

Summaryinfo

A vulnerability was found in Ruckus Wireless 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 up to 200.7.10.92. It has been rated as critical. The affected element is an unknown function of the component rkscli. Performing a manipulation results in os command injection. This vulnerability was named CVE-2020-13917. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability, which was classified as critical, was found in Ruckus Wireless 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 up to 200.7.10.92. This affects an unknown function of the component rkscli. The manipulation with an unknown input leads to a os command injection vulnerability. CWE is classifying the issue as CWE-78. The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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.

The weakness was presented 07/28/2020 (Website). The advisory is shared at support.ruckuswireless.com. This vulnerability is uniquely identified as CVE-2020-13917 since 06/07/2020. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1202 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

See VDB-159029, VDB-159030, VDB-159031 and VDB-159032 for similar entries. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• Ruckus Wireless

Name

• C110
• E510
• H320
• H510
• M510
• R310
• R320
• R500
• R510 R600
• R610
• R710
• R720
• R750
• T300
• T301n
• T301s
• T310c
• T310d
• T310n
• T310s
• T610
• T710
• T710s

Version

• 200.7.10.0
• 200.7.10.1
• 200.7.10.2
• 200.7.10.3
• 200.7.10.4
• 200.7.10.5
• 200.7.10.6
• 200.7.10.7
• 200.7.10.8
• 200.7.10.9
• 200.7.10.10
• 200.7.10.11
• 200.7.10.12
• 200.7.10.13
• 200.7.10.14
• 200.7.10.15
• 200.7.10.16
• 200.7.10.17
• 200.7.10.18
• 200.7.10.19
• 200.7.10.20
• 200.7.10.21
• 200.7.10.22
• 200.7.10.23
• 200.7.10.24
• 200.7.10.25
• 200.7.10.26
• 200.7.10.27
• 200.7.10.28
• 200.7.10.29
• 200.7.10.30
• 200.7.10.31
• 200.7.10.32
• 200.7.10.33
• 200.7.10.34
• 200.7.10.35
• 200.7.10.36
• 200.7.10.37
• 200.7.10.38
• 200.7.10.39
• 200.7.10.40
• 200.7.10.41
• 200.7.10.42
• 200.7.10.43
• 200.7.10.44
• 200.7.10.45
• 200.7.10.46
• 200.7.10.47
• 200.7.10.48
• 200.7.10.49
• 200.7.10.50
• 200.7.10.51
• 200.7.10.52
• 200.7.10.53
• 200.7.10.54
• 200.7.10.55
• 200.7.10.56
• 200.7.10.57
• 200.7.10.58
• 200.7.10.59
• 200.7.10.60
• 200.7.10.61
• 200.7.10.62
• 200.7.10.63
• 200.7.10.64
• 200.7.10.65
• 200.7.10.66
• 200.7.10.67
• 200.7.10.68
• 200.7.10.69
• 200.7.10.70
• 200.7.10.71
• 200.7.10.72
• 200.7.10.73
• 200.7.10.74
• 200.7.10.75
• 200.7.10.76
• 200.7.10.77
• 200.7.10.78
• 200.7.10.79
• 200.7.10.80
• 200.7.10.81
• 200.7.10.82
• 200.7.10.83
• 200.7.10.84
• 200.7.10.85
• 200.7.10.86
• 200.7.10.87
• 200.7.10.88
• 200.7.10.89
• 200.7.10.90
• 200.7.10.91
• 200.7.10.92

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion