CVE-2020-9119

MEDIUM
6.2
CVSS Score
Published: December 24, 2020 at 03:49 PM UTC
Updated: June 17, 2026 at 03:27 AM UTC
10 products affected across 1 vendorMate 30 FirmwareMate 10 FirmwareMate 30 Pro Firmware

Using HUAWEI Mate 10;HUAWEI Mate 30;HUAWEI Mate 30 Pro;HUAWEI P40;HUAWEI P40 Pro by N/A?

Get instant alerts when new vulnerabilities affect HUAWEI Mate 10;HUAWEI Mate 30;HUAWEI Mate 30 Pro;HUAWEI P40;HUAWEI P40 Pro - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.2
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 10.0.0.189(c185e6r1p3)
Affected range stops below 10.0.0.189(c185e6r1p3), so it looks safe — our inference, not a vendor statement
huawei-mate-10 (same device)
v < 10.1.0.156(c00e155r7p2)
Affected range stops below 10.1.0.156(c00e155r7p2), so it looks safe — our inference, not a vendor statement
huawei-mate-30 (same device)
v < 10.1.0.156(c00e156r7p2)
Affected range stops below 10.1.0.156(c00e156r7p2), so it looks safe — our inference, not a vendor statement
huawei-mate-30-pro (same device)
v < 10.1.0.150(sp1c00e150r4p1)
Affected range stops below 10.1.0.150(sp1c00e150r4p1), so it looks safe — our inference, not a vendor statement
huawei-p40 (same device)
v < 10.1.0.150(sp1c00e150r4p1)
Affected range stops below 10.1.0.150(sp1c00e150r4p1), so it looks safe — our inference, not a vendor statement
huawei-p40-pro (same device)
v < 10.0.0.189v < 10.1.0.150v < 10.1.0.156
Affected range stops below 10.0.0.189, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.1.0.150, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.1.0.156, so it looks safe — our inference, not a vendor statement
v < 10.0.0.189v < 10.1.0.150v < 10.1.0.156
Affected range stops below 10.0.0.189, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.1.0.150, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.1.0.156, so it looks safe — our inference, not a vendor statement
v < 10.0.0.189v < 10.1.0.150v < 10.1.0.156
Affected range stops below 10.0.0.189, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.1.0.150, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.1.0.156, so it looks safe — our inference, not a vendor statement
v < 10.0.0.189v < 10.1.0.150v < 10.1.0.156
Affected range stops below 10.0.0.189, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.1.0.150, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.1.0.156, so it looks safe — our inference, not a vendor statement
v < 10.0.0.189v < 10.1.0.150v < 10.1.0.156
Affected range stops below 10.0.0.189, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.1.0.150, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.1.0.156, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

CVSS

Attack Vector
PHYSICAL
Complexity
LOW
Privileges
HIGH
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card