# CVE-2020-9257: Memory corruption in HUAWEI P30 Pro

> A buffer overflow in Huawei P30 Pro allows code execution if a user installs a malicious application, requiring an upgrade to secure the device.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Jul 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-c3h3-5867-mxh8

## What is CVE-2020-9257?

CVE-2020-9257 is a high-severity memory corruption vulnerability in HUAWEI P30 Pro, published on 17 Jul 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

HUAWEI P30 Pro smartphones with versions earlier than 10.1.0.123(C432E19R2P5patch02), versions earlier than 10.1.0.126(C10E11R5P1), and versions earlier than 10.1.0.160(C00E160R2P8) have a buffer overflow vulnerability. The software access data past the end, or before the beginning, of the intended buffer when handling certain operations of certificate, the attacker should trick the user into installing a malicious application, successful exploit may cause code execution.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2020-9257?

It affects 1 product.


Products: Huawei P30 Pro Firmware.

## How do I fix CVE-2020-9257?

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

## Is CVE-2020-9257 being exploited?

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

## Other vulnerabilities in HUAWEI P30 Pro

- [CVE-2020-9123](https://insights.sbomify.com/CVE-2020-9123/): Memory corruption in HUAWEI P30 Pro (high 7.8)
- [CVE-2020-9254](https://insights.sbomify.com/CVE-2020-9254/): Business logic in HUAWEI P30 Pro (high 7.8)
- [CVE-2020-9107](https://insights.sbomify.com/CVE-2020-9107/): Memory corruption in HUAWEI P30 Pro (medium 5.5)
- [CVE-2020-9108](https://insights.sbomify.com/CVE-2020-9108/): Memory corruption in HUAWEI P30 Pro (medium 5.5)
- [CVE-2020-9095](https://insights.sbomify.com/CVE-2020-9095/): Integer overflow in HUAWEI P30 Pro (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-9257 and fix it if it is affected.

What it is: CVE-2020-9257 is a high-severity memory corruption vulnerability in HUAWEI P30 Pro, published on 17 Jul 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-9257 in the wild and no public exploit code.

Affected product: HUAWEI P30 Pro. 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-2020-9257/ (Markdown: https://insights.sbomify.com/CVE-2020-9257/index.md)
```

## Sources

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

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