Some Huawei smart phones have a null pointer dereference vulnerability.
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.91% (FIRST EPSS); higher than 59.4% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Some Huawei smart phones have a null pointer dereference vulnerability. An attacker crafts specific packets and sends to the affected product to exploit this vulnerability. Successful exploitation may cause the affected phone to be abnormal.
- Published
- Dec 13, 2019
- Updated
- Jun 16, 2026
- EPSS
- 0.9% · 59th percentile
- CWE
- CWE-476
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.9%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| huawei | alp-al00b firmware | cpe:2.3:o:huawei:alp-al00b_firmware |
| huawei | alp-al00b | cpe:2.3:h:huawei:alp-al00b |
| huawei | alp-tl00b firmware | cpe:2.3:o:huawei:alp-tl00b_firmware |
| huawei | alp-tl00b | cpe:2.3:h:huawei:alp-tl00b |
| huawei | bla-al00b firmware | cpe:2.3:o:huawei:bla-al00b_firmware |
| huawei | bla-al00b | cpe:2.3:h:huawei:bla-al00b |
| huawei | bla-tl00b firmware | cpe:2.3:o:huawei:bla-tl00b_firmware |
| huawei | bla-tl00b | cpe:2.3:h:huawei:bla-tl00b |
| huawei | charlotte-al00a firmware | cpe:2.3:o:huawei:charlotte-al00a_firmware |
| huawei | charlotte-al00a | cpe:2.3:h:huawei:charlotte-al00a |
| huawei | charlotte-tl00b firmware | cpe:2.3:o:huawei:charlotte-tl00b_firmware |
| huawei | charlotte-tl00b | cpe:2.3:h:huawei:charlotte-tl00b |
and 88 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- huawei alp-al00b firmware8.0.0.153(c00)
- huawei alp-tl00b firmware8.0.0.129(sp2c01)
- huawei bla-al00b firmware8.0.0.129(sp2c786)
- huawei bla-al00b firmware8.0.0.153(c00)
- huawei bla-tl00b firmware8.0.0.129(sp2c01)
- huawei charlotte-al00a firmware8.1.0.176(c00)
- huawei charlotte-tl00b firmware8.1.0.176(c01)
- huawei columbia-al10b firmware8.1.0.163(c00)
- huawei columbia-al10i firmware8.1.0.150(c675custc675d2)
- huawei columbia-l29d firmware8.1.0.146(c461)
- huawei columbia-l29d firmware8.1.0.148(c185)
- huawei columbia-l29d firmware8.1.0.151(c10)
- huawei columbia-l29d firmware8.1.0.151(c432)
- huawei columbia-tl00d firmware8.1.0.186(c01gt)
- huawei elle-al00b firmware9.1.0.162(c00e160r2p1)
- huawei elle-tl00b firmware9.1.0.162(c01e160r2p1)
- huawei emily-al00a firmware8.1.0.190(c00)
- huawei emily-tl00b firmware8.1.0.175(c01)
- huawei ever-al00b firmware9.0.0.195(c00e195r2p1)
- huawei ever-l29b firmware9.0.0.206(c185e3r3p1)
Versions reported by the vendor
Affected version ranges reported by the assigning authority (huawei). Independent of NVD's CPE analysis and usually ahead of it.
n/a Harry-AL00C, Harry-AL00C-PRELOAD, Harry-AL10B, Harry-LGRP1-CHN, Harry-TL00C, Jackman-AL00D, Jackman-L03, Jackman-L21, Jackman-L22, Jackman-L23, Johnson-AL00C, Johnson-AL00IC, Johnson-AL10C, Johnson-L2
- Version, 9.1.0.206(C00E205R3P1), 9.0.1.5(C735R1), 9.1.0.1(C00R3), 9.1.0.206, 9.0.1.162(C01E160R2P3), 8.2.0.170(C861), 8.2.0.188(C00R2P1), 8.2.0.163(C605), 8.2.0.160(C185), 8.2.0.156(C636R2P2), 8.2.0.152(C45CUSTC45D1) … (+28)affected
Same product
huawei: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-7910Some Huawei smartphones ALP-AL00B 8.0.0.118D(C00), ALP-TL00B 8.0.0.118D(C01), BLA-AL00B 8.0.0.118D(C00), BLA-L09C 8.0.0.127(C432), 8.0.0.12827Monitor
- CVE-2019-5303There are two denial of service vulnerabilities on some Huawei smartphones.21Monitor
- CVE-2019-5302There are two denial of service vulnerabilities on some Huawei smartphones.21Monitor
- CVE-2019-19412Huawei smart phones have a Factory Reset Protection (FRP) bypass security vulnerability.18Monitor
- CVE-2018-7911Some Huawei smart phones ALP-AL00B 8.0.0.106(C00), 8.0.0.113(SP2C00), 8.0.0.113(SP3C00), 8.0.0.113(SP7C00), 8.0.0.118(C00), 8.0.0.120(SP2C0018Monitor
- CVE-2018-7901RCS module in Huawei ALP-AL00B smart phones with software versions earlier than 8.0.0.129, BLA-AL00B smart phones with software versions ear17Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- low · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- Low
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.