# CVE-2017-17225: Memory corruption in Mate 9 Pro

> A buffer overflow in the NFC module allows attackers to inject malicious data, potentially causing system restarts or arbitrary code execution on Huawei Mate 9 Pro devices.

- **Severity:** High 8.8 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 9 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4vxw-ghfr-vr8m

## What is CVE-2017-17225?

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

### Official description

The Near Field Communication (NFC) module in Huawei Mate 9 Pro mobile phones with the versions before LON-AL00B 8.0.0.340a(C00) has a buffer overflow vulnerability due to the lack of input validation. An attacker may use an NFC card reader or another device to inject malicious data into a target mobile phone. Successful exploit could lead to system restart or arbitrary code execution.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Huawei Mate 9 Pro Firmware.

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

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

## Is CVE-2017-17225 being exploited?

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

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

- [CVE-2017-17320](https://insights.sbomify.com/CVE-2017-17320/): Use after free in Mate 9 Pro (high 7.8)
- [CVE-2017-17324](https://insights.sbomify.com/CVE-2017-17324/): Integer overflow in Mate 9 Pro (high 7.8)
- [CVE-2017-17279](https://insights.sbomify.com/CVE-2017-17279/): Auth bypass in Mate 9 Pro (medium 5.5)
- [CVE-2017-15347](https://insights.sbomify.com/CVE-2017-15347/): Use after free in Mate 9 Pro (medium 5.5)
- [CVE-2019-5217](https://insights.sbomify.com/CVE-2019-5217/): Auth bypass in Mate 9 Pro (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-17225 is a high-severity memory corruption vulnerability in Huawei Technologies Co., Ltd. Mate 9 Pro, published on 9 Mar 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-17225 in the wild and no public exploit code.

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

## Sources

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

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