# CVE-2020-9119: Privilege escalation in HUAWEI Mate 10;HUAWEI Mate 30;HUAWEI Mate 30 Pro;HUAWEI P40;HUAWEI P40 Pro

> Physical access allows attackers to escalate privileges and execute commands on Huawei smartphones due to design defects.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:P/AC:L/PR:H/UI:N/S:U/C:H/I:H/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:** 24 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-5v7h-9v5g-w2x6

## What is CVE-2020-9119?

CVE-2020-9119 is a medium-severity vulnerability in HUAWEI Mate 10;HUAWEI Mate 30;HUAWEI Mate 30 Pro;HUAWEI P40;HUAWEI P40 Pro, published on 24 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

There is a privilege escalation vulnerability on some Huawei smart phones due to design defects. The attacker needs to physically contact the mobile phone and obtain higher privileges, and execute relevant commands, resulting in the user's privilege promotion.

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

It affects 5 products.


Products: Huawei Mate 10 Firmware, Huawei Mate 30 Firmware, Huawei Mate 30 Pro Firmware, Huawei P40 Firmware, Huawei P40 Pro Firmware.

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

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

## Is CVE-2020-9119 being exploited?

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

## Other vulnerabilities in HUAWEI Mate 10;HUAWEI Mate 30;HUAWEI Mate 30 Pro;HUAWEI P40;HUAWEI P40 Pro

- [CVE-2017-15311](https://insights.sbomify.com/CVE-2017-15311/): Memory corruption in Mate 10 (high 8.8)
- [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-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-2020-9119 and fix it if it is affected.

What it is: CVE-2020-9119 is a medium-severity vulnerability in HUAWEI Mate 10;HUAWEI Mate 30;HUAWEI Mate 30 Pro;HUAWEI P40;HUAWEI P40 Pro, published on 24 Dec 2020. 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-2020-9119 in the wild and no public exploit code.

Affected product: HUAWEI Mate 10;HUAWEI Mate 30;HUAWEI Mate 30 Pro;HUAWEI P40;HUAWEI P40 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-9119/ (Markdown: https://insights.sbomify.com/CVE-2020-9119/index.md)
```

## Sources

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

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