Xiaomi Mi WiFi R3G up to 2.28.22 Backup File /tmp/speedtest_urls.xml input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Xiaomi Mi WiFi R3G up to 2.28.22. This affects an unknown part of the file /tmp/speedtest_urls.xml of the component Backup File Handler. The manipulation leads to input validation. This vulnerability is listed as CVE-2019-18370. The attack may be initiated remotely. There is no available exploit. It is suggested to upgrade the affected component.
Details
A vulnerability was found in Xiaomi Mi WiFi R3G up to 2.28.22 (Wireless LAN Software) and classified as critical. This issue affects an unknown code of the file /tmp/speedtest_urls.xml of the component Backup File Handler. The manipulation with an unknown input 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:
An issue was discovered on Xiaomi Mi WiFi R3G devices before 2.28.23-stable. The backup file is in tar.gz format. After uploading, the application uses the tar zxf command to decompress, so one can control the contents of the files in the decompressed directory. In addition, the application's sh script for testing upload and download speeds reads a URL list from /tmp/speedtest_urls.xml, and there is a command injection vulnerability, as demonstrated by api/xqnetdetect/netspeed.
The weakness was presented 10/23/2019. The identification of this vulnerability is CVE-2019-18370 since 10/23/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 are known, but no exploit is available.
By approaching the search of inurl:tmp/speedtest_urls.xml it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 2.28.23-stable eliminates this vulnerability.
See VDB-144114 for similar entry. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
- 2.28.0
- 2.28.1
- 2.28.2
- 2.28.3
- 2.28.4
- 2.28.5
- 2.28.6
- 2.28.7
- 2.28.8
- 2.28.9
- 2.28.10
- 2.28.11
- 2.28.12
- 2.28.13
- 2.28.14
- 2.28.15
- 2.28.16
- 2.28.17
- 2.28.18
- 2.28.19
- 2.28.20
- 2.28.21
- 2.28.22
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Mi WiFi R3G 2.28.23-stable
Timeline
10/23/2019 🔍10/23/2019 🔍
10/24/2019 🔍
01/27/2024 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2019-18370 (🔍)
GCVE (CVE): GCVE-0-2019-18370
GCVE (VulDB): GCVE-100-144113
See also: 🔍
Entry
Created: 10/24/2019 13:11Updated: 01/27/2024 08:41
Changes: 10/24/2019 13:11 (39), 10/24/2019 13:16 (18), 01/27/2024 08:41 (4)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.