# CVE-2017-15311: Memory corruption in Mate 10

> Attackers can send malicious wireless packets to Huawei smartphones to trigger a stack overflow in the baseband module, enabling remote code execution or denial of service.

- **Severity:** High 8.8 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 22 Dec 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-j9rv-r9r2-7hjg

## What is CVE-2017-15311?

CVE-2017-15311 is a high-severity memory corruption vulnerability in Huawei Technologies Co., Ltd. Mate 10, published on 22 Dec 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The baseband modules of Mate 10, Mate 10 Pro, Mate 9, Mate 9 Pro Huawei smart phones with software before ALP-AL00 8.0.0.120(SP2C00), before BLA-AL00 8.0.0.120(SP2C00), before MHA-AL00B 8.0.0.334(C00), and before LON-AL00B 8.0.0.334(C00) have a stack overflow vulnerability due to the lack of parameter validation. An attacker could send malicious packets to the smart phones within radio range by special wireless device, which leads stack overflow when the baseband module handles these packets. The attacker could exploit this vulnerability to perform a denial of service attack or remote code execution in baseband module.

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

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

It affects 4 products.


Products: Huawei Mate 10 Firmware, Huawei Mate 10 Pro Firmware, Huawei Mate 9 Firmware, Huawei Mate 9 Pro Firmware.

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

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

## Is CVE-2017-15311 being exploited?

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

## Other vulnerabilities in Huawei Technologies Co., Ltd. Mate 10

- [CVE-2018-7993](https://insights.sbomify.com/CVE-2018-7993/): Use after free in HUAWEI Mate 10 (high 7.8)
- [CVE-2017-17227](https://insights.sbomify.com/CVE-2017-17227/): Memory corruption in Mate 10 (high 7.8)
- [CVE-2020-9119](https://insights.sbomify.com/CVE-2020-9119/): Privilege escalation in HUAWEI Mate 10;HUAWEI Mate 30;HUAWEI Mate 30 Pro;HUAWEI P40;HUAWEI P40 Pro (medium 6.2)
- [CVE-2019-5214](https://insights.sbomify.com/CVE-2019-5214/): Use after free in Huawei Mate10 (medium 5.5)
- [CVE-2019-5219](https://insights.sbomify.com/CVE-2019-5219/): Use after free in Mate10 (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-15311 is a high-severity memory corruption vulnerability in Huawei Technologies Co., Ltd. Mate 10, published on 22 Dec 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-15311 in the wild and no public exploit code.

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

## Sources

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

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