CVE-2017-17176
Summary
| CVE | CVE-2017-17176 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2018-10-17 15:29:00 UTC |
| Updated | 2019-10-03 00:03:00 UTC |
| Description | The hardware security module of Mate 9 and Mate 9 Pro Huawei smart phones with the versions earlier before MHA-AL00BC00B156, versions earlier before MHA-CL00BC00B156, versions earlier before MHA-DL00BC00B156, versions earlier before MHA-TL00BC00B156, versions earlier before LON-AL00BC00B156, versions earlier before LON-CL00BC00B156, versions earlier before LON-DL00BC00B156, versions earlier before LON-TL00BC00B156 has a arbitrary memory read/write vulnerability due to the input parameters validation. An attacker with the root privilege of the Android system could exploit this vulnerability to read and write memory data anywhere or execute arbitrary code in the TrustZone. |
Risk And Classification
Problem Types: CWE-787
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Hardware | Huawei | Mate 9 | - | All | All | All |
| Hardware | Huawei | Mate 9 | - | All | All | All |
| Operating System | Huawei | Mate 9 Firmware | All | All | All | All |
| Operating System | Huawei | Mate 9 Firmware | All | All | All | All |
| Hardware | Huawei | Mate 9 Pro | - | All | All | All |
| Hardware | Huawei | Mate 9 Pro | - | All | All | All |
| Operating System | Huawei | Mate 9 Pro Firmware | All | All | All | All |
| Operating System | Huawei | Mate 9 Pro Firmware | All | All | All | All |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| Security Advisory - Arbitrary Memory Read Write Vulnerability in Huawei Smart Phones | CONFIRM | www.huawei.com | Vendor Advisory |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.