# CVE-2018-7911: Security feature bypass in ALP-AL00B, ALP-AL00B-RSC, BLA-TL00B, Charlotte-AL00A, Emily-AL00A, > Attackers can bypass Factory Reset Protection on Huawei smartphones by exploiting the Gaode Map configuration flow to update the Google account. - **Severity:** Medium 4.6 (`CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 23 Oct 2018 - **Updated:** 5 Aug 2024 - **Also known as:** GHSA-vf4f-ww7h-wr5w ## What is CVE-2018-7911? CVE-2018-7911 is a medium-severity vulnerability in Huawei Technologies Co., Ltd. ALP-AL00B, ALP-AL00B-RSC, BLA-TL00B, Charlotte-AL00A, Emily-AL00A,, published on 23 Oct 2018. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description 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. ## Which versions are affected by CVE-2018-7911? It affects 5 products. Products: Huawei Alp-Al00b-Rsc Firmware, Huawei Alp-Al00b Firmware, Huawei Bla-Tl00b Firmware, Huawei Charlotte-Al00a Firmware, Huawei Emily-Al00a Firmware. ## How do I fix CVE-2018-7911? No fix has been published for CVE-2018-7911 yet. Limit exposure of the affected software until one is available. ## Is CVE-2018-7911 being exploited? There is no known exploitation of CVE-2018-7911 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2018-7911 and fix it if it is affected. What it is: CVE-2018-7911 is a medium-severity vulnerability in Huawei Technologies Co., Ltd. ALP-AL00B, ALP-AL00B-RSC, BLA-TL00B, Charlotte-AL00A, Emily-AL00A,, published on 23 Oct 2018. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2018-7911 in the wild and no public exploit code. Affected product: Huawei Technologies Co., Ltd. ALP-AL00B, ALP-AL00B-RSC, BLA-TL00B, Charlotte-AL00A, Emily-AL00A,. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2018-7911/ (Markdown: https://insights.sbomify.com/CVE-2018-7911/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2018-7911 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-7911 - OSV: https://osv.dev/vulnerability/CVE-2018-7911 --- From sbomify Insights: https://insights.sbomify.com/CVE-2018-7911/ Summaries are generated and may contain mistakes; the official description above is the record.