Skip to content
Fencer Intel
medium 6.2

CVE-2020-9119 json

There is a privilege escalation vulnerability on some Huawei smart phones due to design defects.

published 5y ago modified 4mo ago also EUVD-2020-29948

cvss
6.2
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 13%
public exploits
0
none known

Summary

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.

Patch / fix

  • huawei mate_10_firmware 10.0.0.189\(c185e6r1p3\)
  • huawei mate_30_firmware 10.1.0.156\(c00e155r7p2\)
  • huawei mate_30_pro_firmware 10.1.0.156\(c00e156r7p2\)
  • huawei p40_firmware 10.1.0.150\(sp1c00e150r4p1\)
  • huawei p40_pro_firmware 10.1.0.150\(sp1c00e150r4p1\)

Is CVE-2020-9119 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.23% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Affected products

  • n/a HUAWEI Mate 10;HUAWEI Mate 30;HUAWEI Mate 30 Pro;HUAWEI P40;HUAWEI P40 Pro

References

Sources

Fencer Intel 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.