# CVE-2016-8279: Denial of service in n/a

> Attackers can cause a device reboot via a crafted application exploiting a video driver flaw in specific Huawei smartphones.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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:** 26 Sep 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-w78m-r2q8-9j49

## What is CVE-2016-8279?

CVE-2016-8279 is a medium-severity denial of service vulnerability in n/a, published on 26 Sep 2016. 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 video driver in Huawei Mate S smartphones with software CRR-TL00 before CRR-TL00C01B362, CRR-UL20 before CRR-UL20C00B362, CRR-CL00 before CRR-CL00C92B362, and CRR-CL20 before CRR-CL20C92B362; P8 smartphones with software GRA-TL00 before GRA-TL00C01B366, GRA-UL00 before GRA-UL00C00B366, GRA-UL10 before GRA-UL10C00B366, and GRA-CL00 before GRA-CL00C92B366; and Honor 6 and Honor 6 Plus smartphones with software before 6.9.16 allows attackers to cause a denial of service (device reboot) via a crafted application.

Weakness: CWE-284 (Improper Access Control)

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

It affects 3 products.


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

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

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

## Is CVE-2016-8279 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2016-8279 is a medium-severity denial of service vulnerability in n/a, published on 26 Sep 2016. 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-8279 in the wild and no public exploit code.

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

## Sources

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

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