# CVE-2017-8149: Memory corruption in P10, P10 Plus

> A malicious app can trigger a buffer overflow in the bootloader, causing an out-of-bounds read and continuous system reboots on Huawei P10 devices.

- **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:** 22 Nov 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-g6jw-2m24-vm7j

## What is CVE-2017-8149?

CVE-2017-8149 is a medium-severity memory corruption vulnerability in Huawei Technologies Co., Ltd. P10, P10 Plus, 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 boot loaders of P10 and P10 Plus Huawei mobile phones with software the versions before Victoria-L09AC605B162, the versions before Victoria-L29AC605B162, the versions before Vicky-L29AC605B162 have an out-of-bounds memory access vulnerability due to the lack of parameter validation. An attacker with the root privilege of an Android system may trick a user into installing a malicious APP. the APP can modify specific data to cause buffer overflow in the next system reboot, causing out-of-bounds memory read which can continuous system reboot.

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

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

It affects 2 products.


Products: Huawei P10 Firmware, Huawei P10 Plus Firmware.

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

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

## Is CVE-2017-8149 being exploited?

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

## Other vulnerabilities in Huawei Technologies Co., Ltd. P10, P10 Plus

- [CVE-2017-2724](https://insights.sbomify.com/CVE-2017-2724/): Memory corruption in P10 Plus,P10 (high 8.4)
- [CVE-2017-2726](https://insights.sbomify.com/CVE-2017-2726/): Memory corruption in P10 Plus,P10 (high 8.4)
- [CVE-2017-2725](https://insights.sbomify.com/CVE-2017-2725/): Memory corruption in P10 Plus,P10 (high 7.8)
- [CVE-2017-8150](https://insights.sbomify.com/CVE-2017-8150/): Memory corruption in P10, P10 Plus (high 7.8)
- [CVE-2017-8145](https://insights.sbomify.com/CVE-2017-8145/): Denial of service in P10, P10 Plus (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-8149 is a medium-severity memory corruption vulnerability in Huawei Technologies Co., Ltd. P10, P10 Plus, 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-8149 in the wild and no public exploit code.

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

## Sources

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

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