# CVE-2016-8783: Memory corruption in H60 (Honor 6), P9 Plus

> A stack overflow in the touchscreen driver allows attackers to crash the system or escalate privileges via a malicious application.

- **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:** 6 Aug 2024
- **Also known as:** GHSA-g426-8hcq-8h96

## What is CVE-2016-8783?

CVE-2016-8783 is a high-severity memory corruption vulnerability in Huawei Technologies Co., Ltd. H60 (Honor 6), P9 Plus, 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

Touchscreen drive in Huawei H60 (Honor 6) Versions earlier than H60-L02_6.12.16 and P9 Plus Versions earlier than VIE-AL10BC00B356 has a stack overflow vulnerabilities. An attacker tricks a user into installing a malicious application on the smart phone, and send given parameter to touchscreen drive to crash the system or escalate privilege.

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

## Which versions are affected by CVE-2016-8783?

It affects 2 products.


Products: Huawei Honor 6 Firmware, Huawei P9 Plus Firmware.

## How do I fix CVE-2016-8783?

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

## Is CVE-2016-8783 being exploited?

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

## Other vulnerabilities in Huawei Technologies Co., Ltd. H60 (Honor 6), P9 Plus

- [CVE-2016-8759](https://insights.sbomify.com/CVE-2016-8759/): Memory corruption in P9,Honor 6 Versions before EVA-AL10C00B192,Versions before H60-L02 6.10.1 (high 7.8)
- [CVE-2016-8760](https://insights.sbomify.com/CVE-2016-8760/): Memory corruption in P9,Honor 6 Versions before EVA-AL10C00B192,Versions before H60-L02 6.10.1 (high 7.8)
- [CVE-2016-8761](https://insights.sbomify.com/CVE-2016-8761/): Memory corruption in P9,Honor 6 Versions before EVA-AL10C00B192,Versions before H60-L02 6.10.1 (high 7.8)
- [CVE-2016-8768](https://insights.sbomify.com/CVE-2016-8768/): Privilege escalation in Honor 6,Honor 6 Plus,Honor 7 Versions earlier than 6.9.16 (high 7.8)
- [CVE-2016-6179](https://insights.sbomify.com/CVE-2016-6179/): Privilege escalation in n/a (high 7.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-8783 and fix it if it is affected.

What it is: CVE-2016-8783 is a high-severity memory corruption vulnerability in Huawei Technologies Co., Ltd. H60 (Honor 6), P9 Plus, 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-2016-8783 in the wild and no public exploit code.

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

## Sources

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

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