Ruckus Wireless C110 up to 200.7.10.102.92 webs HTTP Request information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered 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.102.92. The impacted element is an unknown function of the component webs. Executing a manipulation as part of HTTP Request can lead to information disclosure. The identification of this vulnerability is CVE-2020-13918. The attack may be launched remotely. There is no exploit available.
Details
A vulnerability has been 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.102.92 and classified as problematic. This vulnerability affects an unknown functionality of the component webs. The manipulation as part of a HTTP Request leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. CVE summarizes:
Incorrect access control in webs in Ruckus Wireless Unleashed through 200.7.10.102.92 allows a remote attacker to leak system information (that can be used for a jailbreak) via an unauthenticated crafted HTTP request. 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 shared 07/28/2020 (Website). The advisory is available at support.ruckuswireless.com. This vulnerability was named CVE-2020-13918 since 06/07/2020. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1592 by the MITRE ATT&CK project.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-159029, VDB-159030, VDB-159031 and VDB-159032 are related to this item. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
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.102.0
- 200.7.10.102.1
- 200.7.10.102.2
- 200.7.10.102.3
- 200.7.10.102.4
- 200.7.10.102.5
- 200.7.10.102.6
- 200.7.10.102.7
- 200.7.10.102.8
- 200.7.10.102.9
- 200.7.10.102.10
- 200.7.10.102.11
- 200.7.10.102.12
- 200.7.10.102.13
- 200.7.10.102.14
- 200.7.10.102.15
- 200.7.10.102.16
- 200.7.10.102.17
- 200.7.10.102.18
- 200.7.10.102.19
- 200.7.10.102.20
- 200.7.10.102.21
- 200.7.10.102.22
- 200.7.10.102.23
- 200.7.10.102.24
- 200.7.10.102.25
- 200.7.10.102.26
- 200.7.10.102.27
- 200.7.10.102.28
- 200.7.10.102.29
- 200.7.10.102.30
- 200.7.10.102.31
- 200.7.10.102.32
- 200.7.10.102.33
- 200.7.10.102.34
- 200.7.10.102.35
- 200.7.10.102.36
- 200.7.10.102.37
- 200.7.10.102.38
- 200.7.10.102.39
- 200.7.10.102.40
- 200.7.10.102.41
- 200.7.10.102.42
- 200.7.10.102.43
- 200.7.10.102.44
- 200.7.10.102.45
- 200.7.10.102.46
- 200.7.10.102.47
- 200.7.10.102.48
- 200.7.10.102.49
- 200.7.10.102.50
- 200.7.10.102.51
- 200.7.10.102.52
- 200.7.10.102.53
- 200.7.10.102.54
- 200.7.10.102.55
- 200.7.10.102.56
- 200.7.10.102.57
- 200.7.10.102.58
- 200.7.10.102.59
- 200.7.10.102.60
- 200.7.10.102.61
- 200.7.10.102.62
- 200.7.10.102.63
- 200.7.10.102.64
- 200.7.10.102.65
- 200.7.10.102.66
- 200.7.10.102.67
- 200.7.10.102.68
- 200.7.10.102.69
- 200.7.10.102.70
- 200.7.10.102.71
- 200.7.10.102.72
- 200.7.10.102.73
- 200.7.10.102.74
- 200.7.10.102.75
- 200.7.10.102.76
- 200.7.10.102.77
- 200.7.10.102.78
- 200.7.10.102.79
- 200.7.10.102.80
- 200.7.10.102.81
- 200.7.10.102.82
- 200.7.10.102.83
- 200.7.10.102.84
- 200.7.10.102.85
- 200.7.10.102.86
- 200.7.10.102.87
- 200.7.10.102.88
- 200.7.10.102.89
- 200.7.10.102.90
- 200.7.10.102.91
- 200.7.10.102.92
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
06/07/2020 🔍07/28/2020 🔍
07/28/2020 🔍
11/05/2020 🔍
Sources
Advisory: support.ruckuswireless.comStatus: Not defined
Confirmation: 🔍
CVE: CVE-2020-13918 (🔍)
GCVE (CVE): GCVE-0-2020-13918
GCVE (VulDB): GCVE-100-159034
See also: 🔍
Entry
Created: 07/28/2020 21:30Updated: 11/05/2020 18:33
Changes: 07/28/2020 21:30 (39), 07/28/2020 21:35 (17), 11/05/2020 18:33 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.