Ruckus Wireless Unleashed up to 200.7.10.102.64 emfd admin/_cmdstat.jsp xcmd os command injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Ruckus Wireless Unleashed up to 200.7.10.102.64. It has been classified as critical. This affects an unknown function of the file admin/_cmdstat.jsp of the component emfd. This manipulation of the argument xcmd as part of POST Request causes os command injection. This vulnerability is registered as CVE-2019-19841. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability was found in Ruckus Wireless Unleashed up to 200.7.10.102.64. It has been declared as critical. Affected by this vulnerability is an unknown code block of the file admin/_cmdstat.jsp of the component emfd. The manipulation of the argument xcmd as part of a POST Request leads to a os command injection vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
emfd in Ruckus Wireless Unleashed through 200.7.10.102.64 allows remote attackers to execute OS commands via a POST request with the attribute xcmd=packet-capture to admin/_cmdstat.jsp via the mac attribute.
The weakness was published 01/22/2020. This vulnerability is known as CVE-2019-19841 since 12/17/2019. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1202 for this issue.
By approaching the search of inurl:admin/_cmdstat.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.
Similar entries are available at VDB-149247, VDB-149246, VDB-149244 and VDB-149243. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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: Os command injectionCWE: CWE-78 / CWE-77 / CWE-74
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-19841 (🔍)
GCVE (CVE): GCVE-0-2019-19841
GCVE (VulDB): GCVE-100-149245
See also: 🔍
Entry
Created: 01/23/2020 08:24Updated: 03/25/2024 10:28
Changes: 01/23/2020 08:24 (39), 01/23/2020 08:29 (17), 03/25/2024 10:28 (17)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.