CVE-2018-7911

MEDIUMNVD 4.64.6—
EchelonGraph scoreMEDIUM confidence

Score 4.6 from GitHub Security Advisory published 2022-05-13. NVD baseline CVSS 4.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
4.6
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.6Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
4.6
EG Score
4.6(medium)
EPSS
14.6%
KEV
Not listed

Published

October 23, 2018

Last Modified

November 21, 2024

References (2)

Data Freshness Timeline

(refreshed 12× in last 7d / 47× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 13:42 UTCEPSS rescore
  2. 2026-07-07 13:42 UTCEPSS rescore
  3. 2026-07-06 16:25 UTCEPSS rescore
  4. 2026-07-06 16:24 UTCEPSS rescore
  5. 2026-07-06 02:20 UTCEPSS rescore
  6. 2026-07-05 02:27 UTCEPSS rescore
  7. 2026-07-04 06:28 UTCEPSS rescore
  8. 2026-07-04 06:28 UTCEPSS rescore
  9. 2026-07-01 15:03 UTCEPSS rescore
  10. 2026-07-01 15:03 UTCEPSS rescore
  11. 2026-06-30 23:20 UTCEPSS rescore
  12. 2026-06-30 23:20 UTCEPSS rescore
  13. 2026-06-29 14:03 UTCEPSS rescore
  14. 2026-06-28 14:04 UTCEPSS rescore
  15. 2026-06-28 04:53 UTCEPSS rescore
  16. 2026-06-28 04:53 UTCEPSS rescore
  17. 2026-06-27 03:06 UTCEPSS rescore
  18. 2026-06-27 03:06 UTCEPSS rescore
  19. 2026-06-25 13:47 UTCEPSS rescore
  20. 2026-06-25 13:47 UTCEPSS rescore
  21. 2026-06-24 14:02 UTCEPSS rescore
  22. 2026-06-24 14:02 UTCEPSS rescore
  23. 2026-06-23 21:30 UTCEPSS rescore
  24. 2026-06-23 21:30 UTCEPSS rescore
  25. 2026-06-22 14:23 UTCEPSS rescore
Show 46 more
  1. 2026-06-22 14:23 UTCEPSS rescore
  2. 2026-06-21 14:54 UTCEPSS rescore
  3. 2026-06-21 14:54 UTCEPSS rescore
  4. 2026-06-21 01:57 UTCEPSS rescore
  5. 2026-06-21 01:57 UTCEPSS rescore
  6. 2026-06-19 19:23 UTCEPSS rescore
  7. 2026-06-19 19:23 UTCEPSS rescore
  8. 2026-06-18 17:50 UTCEPSS rescore
  9. 2026-06-18 17:50 UTCEPSS rescore
  10. 2026-06-17 17:50 UTCEPSS rescore
  11. 2026-06-16 17:50 UTCEPSS rescore
  12. 2026-06-16 17:50 UTCEPSS rescore
  13. 2026-06-15 17:45 UTCEPSS rescore
  14. 2026-06-14 23:15 UTCEPSS rescore
  15. 2026-06-14 23:15 UTCEPSS rescore
  16. 2026-06-13 22:58 UTCEPSS rescore
  17. 2026-06-12 23:09 UTCEPSS rescore
  18. 2026-06-12 23:09 UTCEPSS rescore
  19. 2026-06-11 13:57 UTCEPSS rescore
  20. 2026-06-10 22:16 UTCEPSS rescore
  21. 2026-06-10 13:19 UTCEPSS rescore
  22. 2026-06-08 14:14 UTCEPSS rescore
  23. 2026-06-07 15:22 UTCEPSS rescore
  24. 2026-06-07 15:22 UTCEPSS rescore
  25. 2026-06-06 13:45 UTCEPSS rescore
  26. 2026-06-06 13:45 UTCEPSS rescore
  27. 2026-06-05 22:45 UTCEPSS rescore
  28. 2026-06-05 22:45 UTCEPSS rescore
  29. 2026-06-05 06:08 UTCEPSS rescore
  30. 2026-06-05 06:08 UTCEPSS rescore
  31. 2026-06-04 13:10 UTCEPSS rescore
  32. 2026-06-04 13:10 UTCEPSS rescore
  33. 2026-06-02 20:11 UTCEPSS rescore
  34. 2026-06-01 13:50 UTCEPSS rescore
  35. 2026-05-31 22:29 UTCEPSS rescore
  36. 2026-05-31 22:29 UTCEPSS rescore
  37. 2026-05-29 13:41 UTCEPSS rescore
  38. 2026-05-28 13:43 UTCEPSS rescore
  39. 2026-05-28 13:42 UTCEPSS rescore
  40. 2026-05-28 01:45 UTCEG score recompute
  41. 2026-05-28 01:45 UTCGHSA enrichment
  42. 2026-05-27 13:38 UTCEPSS rescore
  43. 2026-05-26 13:42 UTCEPSS rescore
  44. 2026-05-26 13:42 UTCEPSS rescore
  45. 2026-05-26 07:17 UTCEPSS rescore
  46. 2026-05-26 07:17 UTCEPSS rescore

Frequently asked(5)

What is CVE-2018-7911?
CVE-2018-7911 is a medium vulnerability published on October 23, 2018. 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…
When was CVE-2018-7911 disclosed?
CVE-2018-7911 was first published in the National Vulnerability Database on October 23, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-7911 actively exploited?
CVE-2018-7911 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 14.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2018-7911?
CVE-2018-7911 has a CVSS v3 base score of 4.6 (NVD).
How do I remediate CVE-2018-7911?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-7911, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2018-7911

Explore →

Is Your Infrastructure Affected by CVE-2018-7911?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs