cve.bz

CVE-2020-9239 huawei: Improper Input Validation

5.5 mediumEPSS 0.2%

Medium (5.5) in huawei. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
Huawei smartphones BLA-A09 versions 8.0.0.123(C212),versions earlier than 8.0.0.123(C567),versions earlier than 8.0.0.123(C797);BLA-TL00B versions earlier than 8.1.0.326(C01);Berkeley-L09 versions earlier than 8.0.0.163(C10),versions earlier than 8.0.0.163(C432),Versions earlier than 8.0.0.163(C636),Versions earlier than 8.0.0.172(C10);Duke-L09 versions Duke-L09C10B187, versions Duke-L09C432B189, versions Duke-L09C636B189;HUAWEI P20 versions earlier than 8.0.1.16(C00);HUAWEI P20 Pro versions earlier than 8.1.0.152(C00);Jimmy-AL00A versions earlier than Jimmy-AL00AC00B172;LON-L29D versions LON-L29DC721B192;NEO-AL00D versions earlier than 8.1.0.172(C786);Stanford-AL00 versions Stanford-AL00C00B123;Toronto-AL00 versions earlier than Toronto-AL00AC00B225;Toronto-AL00A versions earlier than Toronto-AL00AC00B225;Toronto-TL10 versions earlier than Toronto-TL10C01B225 have an information vulnerability. A module has a design error that is lack of control of input. Attackers can exploit this vulnerab

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 15th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-20 Improper Input Validation
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2020-9239 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2020-9239?via=ask-ai-copy and https://cve.bz/cve/CVE-2020-9239?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2020-9239 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
huawei:bla-a09_firmware8.0.0.123(c212)
huawei:bla-a09_firmwarebefore 8.0.0.123\(c567\)
huawei:bla-a09_firmwarebefore 8.0.0.123\(c797\)
huawei:bla-tl00b_firmwarebefore 8.1.0.326\(c01\)
huawei:berkeley-l09_firmwarebefore 8.0.0.163\(c10\)
huawei:berkeley-l09_firmwarethrough 8.0.0.163\(c432\)
huawei:berkeley-l09_firmwarebefore 8.0.0.163\(c636\)
huawei:berkeley-l09_firmwarebefore 8.0.0.172\(c10\)
huawei:duke-l09_firmwareduke-l09c10b187
huawei:duke-l09_firmwareduke-l09c432b189
huawei:duke-l09_firmwareduke-l09c636b189
huawei:p20_firmwarebefore 8.0.1.16\(c00\)
huawei:p20_pro_firmwarebefore 8.1.0.152\(c00\)
huawei:jimmy-al00a_firmwarebefore jimmy-al00ac00b172
huawei:lon-l29d_firmwarelon-l29dc721b192
huawei:neo-al00d_firmwarebefore 8.1.0.172\(c786\)
huawei:stanford-al00_firmwarestanford-al00c00b123
huawei:toronto-al00_firmwarebefore toronto-al00ac00b225
huawei:toronto-al00a_firmwarebefore toronto-al00ac00b225
huawei:toronto-tl10_firmwarebefore toronto-tl10c01b225

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).

References

Check your stackJSON