CVE-2018-7911: Some 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(SP2C00…
Noroxi assessment
Priority: Monitor (action score 18/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.23% (FIRST EPSS).
- Physical access to the device is required. 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 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(SP2C00), 8.0.0.125(SP1C00), 8.0.0.125(SP3C00), 8.0.0.126(SP2C00), 8.0.0.126(SP5C00), 8.0.0.127(SP1C00), 8.0.0.128(SP2C00), ALP-AL00B-RSC 1.0.0.2, BLA-TL00B 8.0.0.113(SP7C01), 8.0.0.118(C01), 8.0.0.120(SP2C01), 8.0.0.125(SP1C01), 8.0.0.125(SP2C01), 8.0.0.125(SP3C01), 8.0.0.126(SP2C01), 8.0.0.126(SP5C01), 8.0.0.127(SP1C01), 8.0.0.128(SP2C01), 8.0.0.129(SP2C01), Charlotte-AL00A 8.1.0.105(SP7C00), 8.1.0.106(SP3C00), 8.1.0.107(SP5C00), 8.1.0.107(SP7C00), 8.1.0.108(SP3C00), 8.1.0.108(SP6C00), 8.1.0.109(SP2C00), Emily-AL00A 8.1.0.105(SP6C00), 8.1.0.106(SP2C00), 8.1.0.107(SP5C00), 8.1.0.107(SP7C00), 8.1.0.108(SP2C00), 8.1.0.108(SP6C00), 8.1.0.109(SP5C00) have a Factory Reset Protection (FRP) bypass security vulnerability. When re-configuring the mobile phone using the factory reset protection (FRP) function, an attacker can login the configuration flow by Gaode Map and can perform some operations to update the Google account. As a result, the FRP function is bypassed.
- Published
- Oct 23, 2018
- Updated
- Jun 16, 2026
- EPSS
- 0.2% · 14th percentile
- CWE
- —
Report tools
Action score
18
Low priority for now.
- CVSS
- 18 / 40 · 4.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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.
Is your version affected? Check itNoroxi 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-al00b-rsc firmware | cpe:2.3:o:huawei:alp-al00b-rsc_firmware |
| huawei | alp-al00b-rsc | cpe:2.3:h:huawei:alp-al00b-rsc |
| 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 | emily-al00a firmware | cpe:2.3:o:huawei:emily-al00a_firmware |
| huawei | emily-al00a | cpe:2.3:h:huawei:emily-al00a |
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.
Huawei Technologies Co., Ltd. ALP-AL00B, ALP-AL00B-RSC, BLA-TL00B, Charlotte-AL00A, Emily-AL00A,
- 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(SP2C00), 8.0.0.125(SP1C00), 8.0.0.125(SP3C00), 8.0.0.126(SP2C00), 8.0.0.126(SP5C00), 8.0.0.affected
Affected versions · NVD (20)
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.106(c00)
- huawei alp-al00b firmware8.0.0.113(sp2c00)
- huawei alp-al00b firmware8.0.0.113(sp3c00)
- huawei alp-al00b firmware8.0.0.113(sp7c00)
- huawei alp-al00b firmware8.0.0.118(c00)
- huawei alp-al00b firmware8.0.0.120(sp2c00)
- huawei alp-al00b firmware8.0.0.125(sp1c00)
- huawei alp-al00b firmware8.0.0.125(sp3c00)
- huawei alp-al00b firmware8.0.0.126(sp2c00)
- huawei alp-al00b firmware8.0.0.126(sp5c00)
- huawei alp-al00b firmware8.0.0.127(sp1c00)
- huawei alp-al00b firmware8.0.0.128(sp2c00)
- huawei alp-al00b-rsc firmware1.0.0.2
- huawei bla-tl00b firmware8.0.0.113(sp7c01)
- huawei bla-tl00b firmware8.0.0.118(c01)
- huawei bla-tl00b firmware8.0.0.120(sp2c01)
- huawei bla-tl00b firmware8.0.0.125(sp1c01)
- huawei bla-tl00b firmware8.0.0.125(sp2c01)
- huawei bla-tl00b firmware8.0.0.125(sp3c01)
- huawei bla-tl00b firmware8.0.0.126(sp2c01)
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)…27Monitor
- 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
Published before and after this one in the same product
- ← EarlierCVE-2018-7901Apr 30, 2018 · RCS module in Huawei ALP-AL00B smart phones with software versions earlier than 8.0.0.129, BLA-AL00B smart phones with software versions…17Monitor
- Later →CVE-2019-5235Dec 13, 2019 · Some Huawei smart phones have a null pointer dereference vulnerability.21Monitor
- Later →CVE-2019-19412Jun 8, 2020 · Huawei smart phones have a Factory Reset Protection (FRP) bypass security vulnerability.18Monitor
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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Physical access to the device is required.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Physical
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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 (0)
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.