# CVE-2017-17176: Memory corruption in Mate 9, Mate 9 Pro

> A root-privileged attacker can exploit a memory corruption flaw in the hardware security module to execute arbitrary code in TrustZone.

- **Severity:** Medium 6.7 (`CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Oct 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-2p9x-qhg2-q4vr

## What is CVE-2017-17176?

CVE-2017-17176 is a medium-severity memory corruption vulnerability in Huawei Technologies Co., Ltd. Mate 9, Mate 9 Pro, published on 17 Oct 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2017-17176?

It affects 2 products.


Products: Huawei Mate 9 Firmware, Huawei Mate 9 Pro Firmware.

## How do I fix CVE-2017-17176?

No fix has been published for CVE-2017-17176 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-17176 being exploited?

There is no known exploitation of CVE-2017-17176 in the wild and no public exploit code.

## Other vulnerabilities in Huawei Technologies Co., Ltd. Mate 9, Mate 9 Pro

- [CVE-2017-15316](https://insights.sbomify.com/CVE-2017-15316/): Use after free in Mate 9 (high 7.8)
- [CVE-2017-2716](https://insights.sbomify.com/CVE-2017-2716/): Memory corruption in Mate 9 (high 7.8)
- [CVE-2017-8142](https://insights.sbomify.com/CVE-2017-8142/): Use after free in Mate 9, Mate 9 Pro (high 7.8)
- [CVE-2017-2706](https://insights.sbomify.com/CVE-2017-2706/): Path traversal in Mate 9 (high 7.1)
- [CVE-2017-2707](https://insights.sbomify.com/CVE-2017-2707/): Privilege escalation in Mate 9 (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-17176 and fix it if it is affected.

What it is: CVE-2017-17176 is a medium-severity memory corruption vulnerability in Huawei Technologies Co., Ltd. Mate 9, Mate 9 Pro, published on 17 Oct 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-17176 in the wild and no public exploit code.

Affected product: Huawei Technologies Co., Ltd. Mate 9, Mate 9 Pro. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-17176/ (Markdown: https://insights.sbomify.com/CVE-2017-17176/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-17176
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-17176
- OSV: https://osv.dev/vulnerability/CVE-2017-17176

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-17176/
Summaries are generated and may contain mistakes; the official description above is the record.