Dongguan Diqee Diqee360 Update Process upgrade.sh 7pk security
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in Dongguan Diqee Diqee360. Impacted is an unknown function of the file /mnt/sdcard/$PRO_NAME/upgrade.sh of the component Update Process. The manipulation results in 7pk security. This vulnerability is cataloged as CVE-2018-10988. An attack on the physical device is feasible. There is no exploit available.
Details
A vulnerability was found in Dongguan Diqee Diqee360 (affected version not known). It has been classified as critical. Affected is some unknown functionality of the file /mnt/sdcard/$PRO_NAME/upgrade.sh of the component Update Process. The manipulation with an unknown input leads to a 7pk security vulnerability. CWE is classifying the issue as CWE-254. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
An issue was discovered on Diqee Diqee360 devices. A firmware update process, integrated into the firmware, starts at boot and tries to find the update folder on the microSD card. It executes code, without a digital signature, as root from the /mnt/sdcard/$PRO_NAME/upgrade.sh or /sdcard/upgrage_360/upgrade.sh pathname.
The bug was discovered 06/20/2018. The weakness was shared 07/05/2018 (Website). The advisory is shared for download at gist.github.com. This vulnerability is traded as CVE-2018-10988 since 05/11/2018. The attack needs to be approached locally. The exploitation doesn't require any form of authentication. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 02/25/2020). The MITRE ATT&CK project declares the attack technique as T1211.
The vulnerability was handled as a non-public zero-day exploit for at least 15 days. During that time the estimated underground price was around $5k-$25k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entry VDB-120443 is related to this item. Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.3
VulDB Base Score: 6.8
VulDB Temp Score: 6.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.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: 7pk securityCWE: CWE-254
CAPEC: 🔍
ATT&CK: 🔍
Physical: Yes
Local: Yes
Remote: No
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
05/11/2018 🔍06/20/2018 🔍
07/05/2018 🔍
07/05/2018 🔍
07/06/2018 🔍
02/25/2020 🔍
Sources
Advisory: gist.github.comStatus: Not defined
CVE: CVE-2018-10988 (🔍)
GCVE (CVE): GCVE-0-2018-10988
GCVE (VulDB): GCVE-100-120444
See also: 🔍
Entry
Created: 07/06/2018 08:57Updated: 02/25/2020 23:18
Changes: 07/06/2018 08:57 (58), 02/25/2020 23:18 (1)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.