# CVE-2016-3680: Memory corruption in n/a

> A buffer overflow in the Wi-Fi driver allows attackers to cause a crash or gain privileges via a crafted application on Huawei Mate 8 devices.

- **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:** 26 May 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-chc4-mg8m-pm7q

## What is CVE-2016-3680?

CVE-2016-3680 is a high-severity memory corruption vulnerability in n/a, published on 26 May 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

Buffer overflow in the Wi-Fi driver in Huawei Mate 8 NXT-AL before NXT-AL10C00B182, NXT-CL before NXT-CL00C92B182, NXT-DL before NXT-DL00C17B182, and NXT-TL before NXT-TL00C01B182 allows attackers to cause a denial of service (crash) or possibly gain privileges via a crafted application, aka HWPSIRT-2016-03020.

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

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

It affects 1 product.


Products: Huawei Mate 8 Firmware.

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

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

## Is CVE-2016-3680 being exploited?

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

## Other vulnerabilities in n/a

- [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-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)
- [CVE-2016-8792](https://insights.sbomify.com/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 (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-3680 is a high-severity memory corruption vulnerability in n/a, published on 26 May 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-3680 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-3680/ (Markdown: https://insights.sbomify.com/CVE-2016-3680/index.md)
```

## Sources

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

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