# CVE-2017-17171: Denial of service in HUAWEI Mate 8; HUAWEI P9; HUAWEI P9 Plus

> Attackers can cause system restarts on Huawei smartphones by tricking users into installing a malicious APK that exploits improper parameter processing.

- **Severity:** Medium 4.2 (`CVSS:3.0/AV:L/AC:L/PR:H/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-5fxj-3vg5-qmf8

## What is CVE-2017-17171?

CVE-2017-17171 is a medium-severity denial of service vulnerability in HUAWEI Mate 8; HUAWEI P9; HUAWEI P9 Plus, published on 1 Jun 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

Some Huawei smart phones have the denial of service (DoS) vulnerability due to the improper processing of malicious parameters. An attacker may trick a target user into installing a malicious APK and launch attacks using a pre-installed app with specific permissions. Successful exploit could allow the app to send specific parameters to the smart phone driver, which will result in system restart.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 3 products.


Products: Huawei Mate 8 Firmware, Huawei P9 Firmware, Huawei P9 Plus Firmware.

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

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

## Is CVE-2017-17171 being exploited?

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

## Other vulnerabilities in HUAWEI Mate 8; HUAWEI P9; HUAWEI P9 Plus

- [CVE-2016-5230](https://insights.sbomify.com/CVE-2016-5230/): Auth bypass in n/a (high 8.8)
- [CVE-2016-5231](https://insights.sbomify.com/CVE-2016-5231/): Missing authorization in n/a (high 7.8)
- [CVE-2016-3680](https://insights.sbomify.com/CVE-2016-3680/): Memory corruption in n/a (high 7.8)
- [CVE-2016-3681](https://insights.sbomify.com/CVE-2016-3681/): Memory corruption in n/a (high 7.8)
- [CVE-2016-8791](https://insights.sbomify.com/CVE-2016-8791/): Privilege escalation in Mate 8,Mate S,P8 Versions before NXT-AL10C00B386,Versions before NXT-CL00C92B386,Versions before NXT-DL00C17B386,Versions before NXT-TL00C01B386,Versions before CRR-CL00C92B368,Versions before CRR-CL20C92B368,Versions before CRR-TL00C01B368,Versions before CRR-UL00C00B368,Versions before CRR-UL20C00B368,Versions before GRA-TL00C01B366,Versions before GRA-CL00C92B366,Versions before GRA-CL10C92B366,Versions before GRA-UL00C00B366,Versions before GRA-UL10C00B366 (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-17171 is a medium-severity denial of service vulnerability in HUAWEI Mate 8; HUAWEI P9; HUAWEI P9 Plus, published on 1 Jun 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-17171 in the wild and no public exploit code.

Affected product: HUAWEI Mate 8; HUAWEI P9; HUAWEI P9 Plus. 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-17171/ (Markdown: https://insights.sbomify.com/CVE-2017-17171/index.md)
```

## Sources

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

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