# CVE-2017-8209: Memory corruption in honor 5C,honor 6x

> A buffer overflow in Huawei smartphone drivers allows malicious apps to cause system reboots or execute arbitrary code with root privileges.

- **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:** 22 Nov 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-m434-522w-x9p2

## What is CVE-2017-8209?

CVE-2017-8209 is a high-severity memory corruption vulnerability in Huawei Technologies Co., Ltd. honor 5C,honor 6x, published on 22 Nov 2017. 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

The driver of honor 5C,honor 6x Huawei smart phones with software of versions earlier than NEM-AL10C00B356, versions earlier than Berlin-L21HNC432B360 have a buffer overflow vulnerability due to the lack of parameter validation. An attacker tricks a user into installing a malicious APP which has the root privilege of the Android system, the APP can send a specific parameter to the driver of the smart phone, causing a system reboot 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-8209?

It affects 2 products.


Products: Huawei Honor 5c Firmware, Huawei Honor 6x Firmware.

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

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

## Is CVE-2017-8209 being exploited?

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

## Other vulnerabilities in Huawei Technologies Co., Ltd. honor 5C,honor 6x

- [CVE-2017-8207](https://insights.sbomify.com/CVE-2017-8207/): Memory corruption in honor 5C,honor 6x (high 7.8)
- [CVE-2017-8208](https://insights.sbomify.com/CVE-2017-8208/): Memory corruption in honor 5C,honor 6x (high 7.8)
- [CVE-2017-8210](https://insights.sbomify.com/CVE-2017-8210/): Memory corruption in honor 5C,honor 6x (high 7.8)
- [CVE-2017-8211](https://insights.sbomify.com/CVE-2017-8211/): Memory corruption in honor 5C,honor 6x (high 7.8)
- [CVE-2017-8212](https://insights.sbomify.com/CVE-2017-8212/): Memory corruption in honor 5C,honor 6x (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-8209 is a high-severity memory corruption vulnerability in Huawei Technologies Co., Ltd. honor 5C,honor 6x, published on 22 Nov 2017. 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-8209 in the wild and no public exploit code.

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

## Sources

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

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