# CVE-2016-8792: 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

> Attackers with graphic or camera privileges can crash the system or escalate privileges on affected Huawei smartphones.

- **Severity:** High 7.1 (`CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Apr 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-j5hq-qf3j-7rj7

## What is CVE-2016-8792?

CVE-2016-8792 is a high-severity vulnerability 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, published on 2 Apr 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Huawei Mate 8 phones with software Versions before NXT-AL10C00B386, Versions before NXT-CL00C92B386, Versions before NXT-DL00C17B386, Versions before NXT-TL00C01B386; Mate S phones with software Versions before CRR-CL00C92B368, Versions before CRR-CL20C92B368, Versions before CRR-TL00C01B368, Versions before CRR-UL00C00B368, Versions before CRR-UL20C00B368; and P8 phones with software Versions before GRA-TL00C01B366, Versions before GRA-CL00C92B366, Versions before GRA-CL10C92B366, Versions before GRA-UL00C00B366, Versions before GRA-UL10C00B366 allow attackers with graphic or Camera privilege to crash the system or escalate privilege.

Weakness: CWE-284 (Improper Access Control)

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

It affects 3 products.


Products: Huawei Mate 8 Firmware, Huawei Mate S Firmware, Huawei P8 Firmware.

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

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

## Is CVE-2016-8792 being exploited?

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

## Other vulnerabilities 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

- [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-2016-8792 and fix it if it is affected.

What it is: CVE-2016-8792 is a high-severity vulnerability 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, published on 2 Apr 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-8792 in the wild and no public exploit code.

Affected product: 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. 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-8792/ (Markdown: https://insights.sbomify.com/CVE-2016-8792/index.md)
```

## Sources

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

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