# CVE-2019-5296: Memory corruption in Mate20

> An attacker with high permissions can trigger an out-of-bounds read on Huawei Mate20 devices, causing system instability and potential memory disclosure.

- **Severity:** Low 3.9 (`CVSS:3.0/AV:P/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-5hqc-g8vh-28gg

## What is CVE-2019-5296?

CVE-2019-5296 is a low-severity memory corruption vulnerability in Huawei Mate20, published on 4 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Mate20 Huawei smartphones versions earlier than HMA-AL00C00B175 have an out-of-bounds read vulnerability. An attacker with a high permission runs some specific commands on the smartphone. Due to insufficient input verification, successful exploit may cause out-of-bounds read of the memory and the system abnormal.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Huawei Mate20 Firmware.

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

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

## Is CVE-2019-5296 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-5296 is a low-severity memory corruption vulnerability in Huawei Mate20, published on 4 Jun 2019. 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-2019-5296 in the wild and no public exploit code.

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

## Sources

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

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