CVE-2020-9109

MEDIUM
4.6
CVSS Score
Published: October 12, 2020 at 01:39 PM UTC
Updated: June 17, 2026 at 03:27 AM UTC
12 products affected across 1 vendorMate 20 FirmwareP30 Pro FirmwareMate 20 X Firmware

Using HUAWEI Mate 20;HUAWEI Mate 20 X;HUAWEI P30 Pro;Laya-AL00EP;Tony-AL00B;Tony-TL00B by N/A?

Get instant alerts when new vulnerabilities affect HUAWEI Mate 20;HUAWEI Mate 20 X;HUAWEI P30 Pro;Laya-AL00EP;Tony-AL00B;Tony-TL00B - before attackers find them.

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

Description

There is an information disclosure vulnerability in several smartphones. The device does not sufficiently validate the identity of smart wearable device in certain specific scenario, the attacker need to gain certain information in the victim's smartphone to launch the attack, and successful exploit could cause information disclosure.Affected product versions include:HUAWEI Mate 20 versions earlier than 10.1.0.160(C00E160R3P8),versions earlier than 10.1.0.160(C01E160R2P8);HUAWEI Mate 20 X versions earlier than 10.1.0.160(C00E160R2P8),versions earlier than 10.1.0.160(C01E160R2P8);HUAWEI P30 Pro versions earlier than 10.1.0.160(C00E160R2P8);Laya-AL00EP versions earlier than 10.1.0.160(C786E160R3P8);Tony-AL00B versions earlier than 10.1.0.160(C00E160R2P11);Tony-TL00B versions earlier than 10.1.0.160(C01E160R2P11).

Affected

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

v < 10.1.0.160(c786e160r3p8)
Affected range stops below 10.1.0.160(c786e160r3p8), so it looks safe — our inference, not a vendor statement
huawei-laya-al00ep (same device)
v < 10.1.0.160(c00e160r3p8)v < 10.1.0.160(c01e160r2p8)
Affected range stops below 10.1.0.160(c00e160r3p8), so it looks safe — our inference, not a vendor statement
Affected range stops below 10.1.0.160(c01e160r2p8), so it looks safe — our inference, not a vendor statement
huawei-mate-20 (same device)
v < 10.1.0.160(c00e160r2p8)v < 10.1.0.160(c01e160r2p8)
Affected range stops below 10.1.0.160(c00e160r2p8), so it looks safe — our inference, not a vendor statement
Affected range stops below 10.1.0.160(c01e160r2p8), so it looks safe — our inference, not a vendor statement
huawei-mate-20-x (same device)
v < 10.1.0.160(c00e160r2p8)
Affected range stops below 10.1.0.160(c00e160r2p8), so it looks safe — our inference, not a vendor statement
huawei-p30-pro (same device)
v < 10.1.0.160(c00e160r2p11)
Affected range stops below 10.1.0.160(c00e160r2p11), so it looks safe — our inference, not a vendor statement
huawei-tony-al00b (same device)
v < 10.1.0.160(c01e160r2p11)
Affected range stops below 10.1.0.160(c01e160r2p11), so it looks safe — our inference, not a vendor statement
huawei-tony-tl00b (same device)
v < 10.1.0.160
Affected range stops below 10.1.0.160, so it looks safe — our inference, not a vendor statement
v < 10.1.0.160
Affected range stops below 10.1.0.160, so it looks safe — our inference, not a vendor statement
v < 10.1.0.160
Affected range stops below 10.1.0.160, so it looks safe — our inference, not a vendor statement
v < 10.1.0.160
Affected range stops below 10.1.0.160, 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
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-287

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