Skip to content
Fencer Vulns
medium 4.6

CVE-2020-9109 json

There is an information disclosure vulnerability in several smartphones.

published 2020-10-12 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-29938

cvss
4.6
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 12%
public exploits
0
none known

Summary

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).

Patch / fix

  • huawei mate_20_firmware 10.1.0.160\(c00e160r3p8\), 10.1.0.160\(c01e160r2p8\)
  • huawei mate_20_x_firmware 10.1.0.160\(c00e160r2p8\), 10.1.0.160\(c01e160r2p8\)
  • huawei p30_pro_firmware 10.1.0.160\(c00e160r2p8\)
  • huawei laya-al00ep_firmware 10.1.0.160\(c786e160r3p8\)
  • huawei tony-al00b_firmware 10.1.0.160\(c00e160r2p11\)
  • huawei tony-tl00b_firmware 10.1.0.160\(c01e160r2p11\)

Exploit prediction

0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 4.6 CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 1.9 AV:L/AC:M/Au:N/C:P/I:N/A:N

Affected products

  • n/a HUAWEI Mate 20;HUAWEI Mate 20 X;HUAWEI P30 Pro;Laya-AL00EP;Tony-AL00B;Tony-TL00B

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.