# CVE-2017-8179: Memory corruption in Nice-AL00

> A buffer overflow in the MTK camera driver allows attackers to escalate privileges by tricking users into installing 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:** 22 Nov 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-hgxx-42w2-h2hx

## What is CVE-2017-8179?

CVE-2017-8179 is a high-severity memory corruption vulnerability in Huawei Technologies Co., Ltd. Nice-AL00, published on 22 Nov 2017. 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 camera driver of MTK platform in Huawei smart phones with software of versions earlier than Nice-AL00C00B155 has a buffer overflow vulnerability.Due to the insufficient input verification, an attacker tricks a user into installing a malicious application which has special privilege and sends a specific parameter to the driver of the smart phone, causing privilege escalation.

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

## Which versions are affected by CVE-2017-8179?

It affects 1 product.


Products: Huawei Mtk Platform Smart Phone Firmware.

## How do I fix CVE-2017-8179?

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

## Is CVE-2017-8179 being exploited?

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

## Other vulnerabilities in Huawei Technologies Co., Ltd. Nice-AL00

- [CVE-2017-8180](https://insights.sbomify.com/CVE-2017-8180/): Memory corruption in Nice-AL00 (high 7.8)
- [CVE-2017-8181](https://insights.sbomify.com/CVE-2017-8181/): Memory corruption in Nice-AL00 (high 7.8)
- [CVE-2017-8182](https://insights.sbomify.com/CVE-2017-8182/): Memory corruption in Nice-AL00 (medium 6.1)
- [CVE-2017-8183](https://insights.sbomify.com/CVE-2017-8183/): Information disclosure in Nice-AL00 (medium 5.5)
- [CVE-2017-8184](https://insights.sbomify.com/CVE-2017-8184/): Information disclosure in Nice-AL00 (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-8179 and fix it if it is affected.

What it is: CVE-2017-8179 is a high-severity memory corruption vulnerability in Huawei Technologies Co., Ltd. Nice-AL00, published on 22 Nov 2017. 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-2017-8179 in the wild and no public exploit code.

Affected product: Huawei Technologies Co., Ltd. Nice-AL00. 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-2017-8179/ (Markdown: https://insights.sbomify.com/CVE-2017-8179/index.md)
```

## Sources

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

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