CVE-2020-1839

What it is

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.

At a glance

Exploitability

Can be exploited locally on the machine with an admin-level account, but needs a user to act. High risk of data exposure, data tampering, service disruption.

Exploit odds

0.2% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2020-07-06 19:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 03:02 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.2% in the next 30 days (EPSS).
• Severity: 6.3 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2020-07-06 19:15 UTC

Last modified

2026-06-17 03:02 UTC

Exploit probability

0.2% · EPSS, next 30 days

Weakness

CWE-362 · Race condition

Record status

Modified

Affected

• Huawei Mate 30 Firmware < 10.1.0.150\(c00e136r5p3\)

Attack profile CVSS 3.1 · 6.3

Attack vector

Local

Complexity

High

Privileges needed

High

User interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2020-1839.md and follow it. Check whether this project is affected by CVE-2020-1839. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge