Skip to content
Fencer Intel
medium 4.3

CVE-2020-9104 json

HUAWEI P30 smartphones with Versions earlier than 10.1.0.123(C431E22R2P5),Versions earlier than 10.1.0.123(C432E22R2P5),Versions earlier th…

published 6y ago modified 4mo ago also EUVD-2020-29933

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

Summary

HUAWEI P30 smartphones with Versions earlier than 10.1.0.123(C431E22R2P5),Versions earlier than 10.1.0.123(C432E22R2P5),Versions earlier than 10.1.0.126(C10E7R5P1),Versions earlier than 10.1.0.126(C185E4R7P1),Versions earlier than 10.1.0.126(C461E7R3P1),Versions earlier than 10.1.0.126(C605E19R1P3),Versions earlier than 10.1.0.126(C636E7R3P4),Versions earlier than 10.1.0.128(C635E3R2P4),Versions earlier than 10.1.0.160(C00E160R2P11),Versions earlier than 10.1.0.160(C01E160R2P11) have a denial of service vulnerability. In specific scenario, due to the improper resource management and memory leak of some feature, the attacker could exploit this vulnerability to cause the device reset.

Patch / fix

  • huawei p30_firmware 10.1.0.123\(c431e22r2p5\), 10.1.0.123\(c432e22r2p5\), 10.1.0.126\(c10e7r5p1\), 10.1.0.126\(c185e4r7p1\), 10.1.0.126\(c461e7r3p1\), 10.1.0.126\(c605e19r1p3\), 10.1.0.126\(c636e7r3p4\), 10.1.0.128\(c635e3r2p4\), 10.1.0.160\(c00e160r2p11\), 10.1.0.160\(c01e160r2p11\)

Is CVE-2020-9104 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.32% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Affected products

  • n/a HUAWEI P30

Classification

Weakness
  • CWE-401 Missing Release of Memory after Effective Lifetime

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.