Xiaomi R3600 up to 1.0.65 set_WAN6 Interface privileges management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.9 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Xiaomi R3600 up to 1.0.65. This affects an unknown part of the component set_WAN6 Interface. The manipulation leads to privileges management. This vulnerability is documented as CVE-2020-14100. The attack can be initiated remotely. There is not any exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability was found in Xiaomi R3600 up to 1.0.65 and classified as critical. This issue affects an unknown functionality of the component set_WAN6 Interface. The manipulation with an unknown input leads to a privileges management vulnerability. Using CWE to declare the problem leads to CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
In Xiaomi router R3600 ROM version<1.0.66, filters in the set_WAN6 interface can be bypassed, causing remote code execution. The router administrator can gain root access from this vulnerability.
The weakness was released 09/11/2020 (Website). The advisory is shared at privacy.mi.com. The identification of this vulnerability is CVE-2020-14100 since 06/15/2020. The attack may be initiated remotely. The successful exploitation needs a simple authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
Upgrading to version 1.0.66 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
- 1.0.0
- 1.0.1
- 1.0.2
- 1.0.3
- 1.0.4
- 1.0.5
- 1.0.6
- 1.0.7
- 1.0.8
- 1.0.9
- 1.0.10
- 1.0.11
- 1.0.12
- 1.0.13
- 1.0.14
- 1.0.15
- 1.0.16
- 1.0.17
- 1.0.18
- 1.0.19
- 1.0.20
- 1.0.21
- 1.0.22
- 1.0.23
- 1.0.24
- 1.0.25
- 1.0.26
- 1.0.27
- 1.0.28
- 1.0.29
- 1.0.30
- 1.0.31
- 1.0.32
- 1.0.33
- 1.0.34
- 1.0.35
- 1.0.36
- 1.0.37
- 1.0.38
- 1.0.39
- 1.0.40
- 1.0.41
- 1.0.42
- 1.0.43
- 1.0.44
- 1.0.45
- 1.0.46
- 1.0.47
- 1.0.48
- 1.0.49
- 1.0.50
- 1.0.51
- 1.0.52
- 1.0.53
- 1.0.54
- 1.0.55
- 1.0.56
- 1.0.57
- 1.0.58
- 1.0.59
- 1.0.60
- 1.0.61
- 1.0.62
- 1.0.63
- 1.0.64
- 1.0.65
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.3VulDB Meta Temp Score: 9.1
VulDB Base Score: 8.8
VulDB Temp Score: 8.4
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: Privileges managementCWE: CWE-269 / 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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: R3600 1.0.66
Timeline
06/15/2020 🔍09/11/2020 🔍
09/11/2020 🔍
09/11/2020 🔍
Sources
Advisory: privacy.mi.comStatus: Not defined
CVE: CVE-2020-14100 (🔍)
GCVE (CVE): GCVE-0-2020-14100
GCVE (VulDB): GCVE-100-161141
Entry
Created: 09/11/2020 21:48Updated: 09/11/2020 21:53
Changes: 09/11/2020 21:48 (39), 09/11/2020 21:53 (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.