# CVE-2016-8775: Memory corruption in NEM Versions before NEM-AL10C00B130,Versions before NEM-UL10C17B160,Versions before NEM-UL10C00B160,Versions before NEM-TL00C01B160,

> A buffer overflow in the Touch Panel driver allows attackers to execute arbitrary code or gain root privileges on Huawei NEM phones.

- **Severity:** Medium 6.7 (`CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Apr 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-cvcr-j4p6-mmrr

## What is CVE-2016-8775?

CVE-2016-8775 is a medium-severity memory corruption vulnerability in NEM Versions before NEM-AL10C00B130,Versions before NEM-UL10C17B160,Versions before NEM-UL10C00B160,Versions before NEM-TL00C01B160,, published on 2 Apr 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Touch Panel (TP) driver in Huawei NEM phones with software Versions before NEM-AL10C00B130, Versions before NEM-UL10C17B160, Versions before NEM-UL10C00B160, Versions before NEM-TL00C01B160 allows attackers to get root privilege or crash the system or execute arbitrary code, related to a buffer overflow.

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

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

It affects 4 products.


Products: Huawei Nem-Al10 Firmware, Huawei Nem-L21 Firmware, Huawei Nem-L22 Firmware, Huawei Nem-L51 Firmware.

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

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

## Is CVE-2016-8775 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2016-8775 is a medium-severity memory corruption vulnerability in NEM Versions before NEM-AL10C00B130,Versions before NEM-UL10C17B160,Versions before NEM-UL10C00B160,Versions before NEM-TL00C01B160,, published on 2 Apr 2017. 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-2016-8775 in the wild and no public exploit code.

Affected product: NEM Versions before NEM-AL10C00B130,Versions before NEM-UL10C17B160,Versions before NEM-UL10C00B160,Versions before NEM-TL00C01B160,. 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-8775/ (Markdown: https://insights.sbomify.com/CVE-2016-8775/index.md)
```

## Sources

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

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