| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Huawei P9 and Honor 6. This vulnerability affects unknown code of the component Touchscreen Driver. Performing a manipulation results in memory corruption. This vulnerability is identified as CVE-2016-8760. The attack is only possible with local access. There is not any exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as critical, was found in Huawei P9 and Honor 6 (Smartphone Operating System) (the affected version is unknown). This affects an unknown code of the component Touchscreen Driver. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Touchscreen driver in Huawei P9 phones with software versions before EVA-AL10C00B192 and Huawei Honor 6 phones with software versions before H60-L02_6.10.1 has a heap overflow vulnerability, which allows attackers to crash the system or escalate user privilege.
The bug was discovered 10/12/2016. The weakness was released 04/02/2017 with Qihoo 360 (Website). The advisory is shared at huawei.com. This vulnerability is uniquely identified as CVE-2016-8760 since 10/18/2016. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. 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 172 days. During that time the estimated underground price was around $5k-$25k.
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 93530†). Entries connected to this vulnerability are available at VDB-99200 and VDB-99202. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
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
10/12/2016 🔍10/12/2016 🔍
10/18/2016 🔍
04/02/2017 🔍
04/02/2017 🔍
04/03/2017 🔍
11/24/2022 🔍
Sources
Vendor: huawei.comAdvisory: sa-20161012-01
Organization: Qihoo 360
Status: Not defined
Confirmation: 🔍
CVE: CVE-2016-8760 (🔍)
GCVE (CVE): GCVE-0-2016-8760
GCVE (VulDB): GCVE-100-99201
SecurityFocus: 93530 - Multiple Huawei Smart Phones Drivers Stack Buffer Overflow and Heap Buffer Overflow Vulnerabilities
OSVDB: - CVE-2016-8760 - Huawei - Multiple Products - Buffer Overflow Issue
See also: 🔍
Entry
Created: 04/03/2017 09:03Updated: 11/24/2022 14:22
Changes: 04/03/2017 09:03 (61), 08/25/2020 08:47 (6), 11/24/2022 14:22 (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.