| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Huawei P10 and P10 Plus. This affects an unknown function. This manipulation causes array index. The identification of this vulnerability is CVE-2017-8172. The attack can only be executed locally. There is no exploit available. You should upgrade the affected component.
Details
A vulnerability classified as critical was found in Huawei P10 and P10 Plus (Smartphone Operating System) (affected version not known). Affected by this vulnerability is some unknown functionality. The manipulation with an unknown input leads to a array index vulnerability. The CWE definition for the vulnerability is CWE-129. The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Isub service in P10 Plus and P10 smart phones with earlier than VKY-AL00C00B157 versions and earlier than VTR-AL00C00B157 versions has a denial of service (DoS) vulnerability. An attacker tricks a user into installing a malicious application on the smart phone, and the application can send given parameter to specific interface, which make a out-of-bounds array access that results in smart phone restart.
The bug was discovered 06/28/2017. The weakness was shared 11/22/2017 by Zhou Ye, Xu Lei Yong and Li Bo with 360 Vulpecker Team (Website). The advisory is shared at huawei.com. This vulnerability is known as CVE-2017-8172 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 147 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 99370†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
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: Array indexCWE: CWE-129 / 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 🔍06/28/2017 🔍
07/03/2017 🔍
11/22/2017 🔍
11/22/2017 🔍
11/23/2017 🔍
01/16/2023 🔍
Sources
Vendor: huawei.comAdvisory: sa-20170628-01
Researcher: Zhou Ye, Xu Lei Yong, Li Bo
Organization: 360 Vulpecker Team
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-8172 (🔍)
GCVE (CVE): GCVE-0-2017-8172
GCVE (VulDB): GCVE-100-109909
SecurityFocus: 99370 - Multiple Huawei Products CVE-2017-8172 Denial of Service Vulnerability
Entry
Created: 11/23/2017 16:45Updated: 01/16/2023 07:57
Changes: 11/23/2017 16:45 (63), 12/10/2019 10:16 (2), 01/16/2023 07:57 (4)
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.