# CVE-2017-2697: Memory corruption in n/a

> A buffer overflow in the goldeneye driver allows a malicious app to crash the system or escalate privileges on affected Huawei Android 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:** 22 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jhvq-9x2q-6898

## What is CVE-2017-2697?

CVE-2017-2697 is a high-severity memory corruption vulnerability in n/a, 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 goldeneye driver in NMO-L31C432B120 and earlier versions,NEM-L21C432B100 and earlier versions,NEM-L51C432B120 and earlier versions,KNT-AL10C746B160 and earlier versions,VNS-L21C185B142 and earlier versions,CAM-L21C10B130 and earlier versions,CAM-L21C185B141 and earlier versions has buffer overflow vulnerability. An attacker with the root privilege of the Android system can tricks a user into installing a malicious application on the smart phone, and send given parameter to smart phone to crash the system or escalate privilege.

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

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

It affects 5 products.


Products: Huawei Gt3 Firmware, Huawei Honor 5c Firmware, Huawei Knt Firmware, Huawei P9 Lite Firmware, Huawei Y6ii Firmware.

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

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

## Is CVE-2017-2697 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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