# CVE-2019-19398: Memory corruption in M5 lite 10

> Attackers can execute malicious code on Huawei M5 Lite 10 devices by exploiting insufficient input validation to modify device memory.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xwgx-57pc-54mp

## What is CVE-2019-19398?

CVE-2019-19398 is a critical memory corruption vulnerability in Huawei M5 lite 10, published on 26 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

M5 lite 10 with versions of 8.0.0.182(C00) have an insufficient input validation vulnerability. Due to the input validation logic is incorrect, an attacker can exploit this vulnerability to modify the memory of the device by doing a series of operations. Successful exploit may lead to malicious code execution.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2019-19398?

It affects 1 product.


Products: Huawei M5 Lite 10 Firmware.

## How do I fix CVE-2019-19398?

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

## Is CVE-2019-19398 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-19398 and fix it if it is affected.

What it is: CVE-2019-19398 is a critical memory corruption vulnerability in Huawei M5 lite 10, published on 26 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-19398 in the wild and no public exploit code.

Affected product: Huawei M5 lite 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-2019-19398/ (Markdown: https://insights.sbomify.com/CVE-2019-19398/index.md)
```

## Sources

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

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