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 |
A vulnerability was found in Huawei Honor 5C and Honor 6X (version unknown). It has been declared as critical. This vulnerability affects an unknown function 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. CVE summarizes:
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 disclosed 11/22/2017 (Website). The advisory is available at huawei.com. This vulnerability was named CVE-2017-8207 since 04/25/2017. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. The technical details are unknown and an exploit is not 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.
The entries 109943, 109944, 109945 and 109946 are pretty similar.
Product
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB CVSS-B Score: 🔍VulDB CVSS-BT Score: 🔍
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: 🔍
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: 🔍
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-8207 (🔍)
See also: 🔍
Entry
Created: 11/23/2017 19:36Updated: 01/16/2023 09:39
Changes: 11/23/2017 19:36 (58), 12/10/2019 15:07 (2), 01/16/2023 09:39 (4)
Complete: 🔍
Cache ID: 52:093
No comments yet. Languages: en.
Please log in to comment.