Huawei Honor 5C/Honor 6X Driver Parameter memory corruption

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Huawei Honor 5C and Honor 6X and classified as critical. Affected by this vulnerability is an unknown functionality of the component Driver. This manipulation as part of Parameter causes memory corruption. This vulnerability is registered as CVE-2017-8210. The attack needs to be launched locally. No exploit is available. The affected component should be upgraded.
Details
A vulnerability classified as critical was found in Huawei Honor 5C and Honor 6X (the affected version unknown). Affected by this vulnerability is an unknown part of the component Driver. The manipulation as part of a Parameter leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
The driver of honor 5C,honor 6x Huawei smart phones with software of versions earlier than NEM-AL10C00B356, versions earlier than Berlin-L21HNC432B360 have a buffer overflow vulnerability due to the lack of parameter validation. An attacker tricks a user into installing a malicious APP which has the root privilege of the Android system, the APP can send a specific parameter to the driver of the smart phone, causing a system reboot or arbitrary code execution.
The bug was discovered 08/04/2017. The weakness was published 11/22/2017 (Website). The advisory is shared at huawei.com. This vulnerability is known as CVE-2017-8210 since 04/25/2017. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 110 days. During that time the estimated underground price was around $5k-$25k.
Upgrading eliminates this vulnerability.
Similar entries are available at VDB-109942, VDB-109943, VDB-109944 and VDB-109946. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
License
Website
- Vendor: https://www.huawei.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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: 🔍
Timeline
04/25/2017 🔍08/04/2017 🔍
11/22/2017 🔍
11/22/2017 🔍
11/23/2017 🔍
01/16/2023 🔍
Sources
Vendor: huawei.comAdvisory: sa-20170801-01
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-8210 (🔍)
GCVE (CVE): GCVE-0-2017-8210
GCVE (VulDB): GCVE-100-109945
See also: 🔍
Entry
Created: 11/23/2017 19:36Updated: 01/16/2023 09:47
Changes: 11/23/2017 19:36 (58), 12/10/2019 15:10 (2), 01/16/2023 09:47 (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.