# CVE-2020-1839: Race condition in HUAWEI Mate 30

> A race condition in HUAWEI Mate 30 allows attackers to execute arbitrary code by tricking users into running a crafted high-privilege application.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Jul 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-7qcq-7635-mr77

## What is CVE-2020-1839?

CVE-2020-1839 is a medium-severity vulnerability in HUAWEI Mate 30, published on 6 Jul 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

HUAWEI Mate 30 with versions earlier than 10.1.0.150(C00E136R5P3) have a race condition vulnerability. There is a timing window exists in which certain pointer members can be modified by another process that is operating concurrently, an attacker should trick the user into running a crafted application with high privilege, successful exploit could cause code execution.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

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

It affects 1 product.


Products: Huawei Mate 30 Firmware.

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

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

## Is CVE-2020-1839 being exploited?

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

## Other vulnerabilities in HUAWEI Mate 30

- [CVE-2020-9263](https://insights.sbomify.com/CVE-2020-9263/): Use after free in HUAWEI Mate 30;HUAWEI P30 (high 7.8)
- [CVE-2020-9261](https://insights.sbomify.com/CVE-2020-9261/): Memory corruption in HUAWEI Mate 30 (high 7.8)
- [CVE-2020-9262](https://insights.sbomify.com/CVE-2020-9262/): Use after free in HUAWEI Mate 30 (high 7.8)
- [CVE-2021-22301](https://insights.sbomify.com/CVE-2021-22301/): Memory corruption in HUAWEI Mate 30 (medium 6.7)
- [CVE-2020-9125](https://insights.sbomify.com/CVE-2020-9125/): Memory corruption in HUAWEI Mate 30 (medium 6.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-1839 is a medium-severity vulnerability in HUAWEI Mate 30, published on 6 Jul 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-1839 in the wild and no public exploit code.

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

## Sources

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

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