Ruckus Wireless Unleashed up to 200.7.10.102.64 zap tools/_rcmdstat.jsp AjaxRestrictedCmdStat POST Request input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Ruckus Wireless Unleashed up to 200.7.10.102.64 and classified as critical. The affected element is the function AjaxRestrictedCmdStat of the file tools/_rcmdstat.jsp of the component zap. The manipulation as part of POST Request leads to input validation.
This vulnerability is listed as CVE-2019-19836. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability was found in Ruckus Wireless Unleashed up to 200.7.10.102.64 and classified as critical. This issue affects the function AjaxRestrictedCmdStat of the file tools/_rcmdstat.jsp of the component zap. The manipulation as part of a POST Request leads to a input validation vulnerability. Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
AjaxRestrictedCmdStat in zap in Ruckus Wireless Unleashed through 200.7.10.102.64 allows remote code execution via a POST request that uses tools/_rcmdstat.jsp to write to a specified filename.
The weakness was presented 01/22/2020. The identification of this vulnerability is CVE-2019-19836 since 12/17/2019. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit.
By approaching the search of inurl:tools/_rcmdstat.jsp it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
See VDB-149247, VDB-149246, VDB-149245 and VDB-149244 for similar entries. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
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
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.5
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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: Input validationCWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
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
12/17/2019 🔍01/22/2020 🔍
01/23/2020 🔍
03/25/2024 🔍
Sources
Advisory: alephsecurity.comStatus: Not defined
CVE: CVE-2019-19836 (🔍)
GCVE (CVE): GCVE-0-2019-19836
GCVE (VulDB): GCVE-100-149243
See also: 🔍
Entry
Created: 01/23/2020 08:18Updated: 03/25/2024 10:16
Changes: 01/23/2020 08:18 (39), 01/23/2020 08:23 (17), 03/25/2024 10:16 (17)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.