# CVE-2017-17227: Memory corruption in Mate 10

> A malicious app can trigger out-of-bounds memory access in the GPU driver, leading to arbitrary code execution or device crashes.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jjgw-phq5-5f8w

## What is CVE-2017-17227?

CVE-2017-17227 is a high-severity memory corruption vulnerability in Huawei Technologies Co., Ltd. Mate 10, published on 9 Mar 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

GPU driver in Huawei Mate 10 smart phones with the versions before ALP-L09 8.0.0.120(C212); The versions before ALP-L09 8.0.0.127(C900); The versions before ALP-L09 8.0.0.128(402/C02/C109/C346/C432/C652) has a out-of-bounds memory access vulnerability due to the input parameters validation. An attacker tricks a user into installing a malicious application on the smart phone, and the application can call the driver with special parameter and cause accessing out-of-bounds memory. Successful exploit may result in phone crash or arbitrary code execution.

Weakness: CWE-787 (Out-of-bounds Write), CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Huawei Mate 10 Firmware.

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

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

## Is CVE-2017-17227 being exploited?

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

## Other vulnerabilities in Huawei Technologies Co., Ltd. Mate 10

- [CVE-2017-15311](https://insights.sbomify.com/CVE-2017-15311/): Memory corruption in Mate 10 (high 8.8)
- [CVE-2018-7993](https://insights.sbomify.com/CVE-2018-7993/): Use after free in HUAWEI Mate 10 (high 7.8)
- [CVE-2020-9119](https://insights.sbomify.com/CVE-2020-9119/): Privilege escalation in HUAWEI Mate 10;HUAWEI Mate 30;HUAWEI Mate 30 Pro;HUAWEI P40;HUAWEI P40 Pro (medium 6.2)
- [CVE-2019-5214](https://insights.sbomify.com/CVE-2019-5214/): Use after free in Huawei Mate10 (medium 5.5)
- [CVE-2019-5219](https://insights.sbomify.com/CVE-2019-5219/): Use after free in Mate10 (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-17227 is a high-severity memory corruption vulnerability in Huawei Technologies Co., Ltd. Mate 10, published on 9 Mar 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-17227 in the wild and no public exploit code.

Affected product: Huawei Technologies Co., Ltd. Mate 10. 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-17227/ (Markdown: https://insights.sbomify.com/CVE-2017-17227/index.md)
```

## Sources

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

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