# CVE-2018-7910: Auth bypass in ALP-AL00B, ALP-TL00B, BLA-AL00B, BLA-L09C, BLA-L29C

> Attackers with physical access can bypass authentication to replace startup programs, gaining control and reading data on Huawei smartphones.

- **Severity:** Medium 6.8 (`CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 13 Nov 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-ppxp-5c57-gjq2

## What is CVE-2018-7910?

CVE-2018-7910 is a medium-severity authentication bypass vulnerability in Huawei Technologies Co., Ltd. ALP-AL00B, ALP-TL00B, BLA-AL00B, BLA-L09C, BLA-L29C, published on 13 Nov 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Some 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.128(C432), 8.0.0.137(C432), BLA-L29C 8.0.0.129(C432), 8.0.0.137(C432) have an authentication bypass vulnerability. When the attacker obtains the user's smartphone, the vulnerability can be used to replace the start-up program so that the attacker can obtain the information in the smartphone and achieve the purpose of controlling the smartphone.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2018-7910?

It affects 5 products.


Products: Huawei Alp-Al00b Firmware, Huawei Alp-Tl00b Firmware, Huawei Bla-Al00b Firmware, Huawei Bla-L09c Firmware, Huawei Bla-L29c Firmware.

## How do I fix CVE-2018-7910?

No fix has been published for CVE-2018-7910 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-7910 being exploited?

There is no known exploitation of CVE-2018-7910 in the wild and no public exploit code.

## Other vulnerabilities in Huawei Technologies Co., Ltd. ALP-AL00B, ALP-TL00B, BLA-AL00B, BLA-L09C, BLA-L29C

- [CVE-2019-5302](https://insights.sbomify.com/CVE-2019-5302/): Denial of service in ALP-AL00B (medium 5.3)
- [CVE-2019-5303](https://insights.sbomify.com/CVE-2019-5303/): Denial of service in ALP-AL00B (medium 5.3)
- [CVE-2019-5235](https://insights.sbomify.com/CVE-2019-5235/): Null dereference in 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-L21C, Johnson-L21D, Johnson-L22C, Johnson-L22D, Johnson-L23C, Johnson-L42IC, Johnson-L42IE, Johnson-L42IF, Johnson-TL00D, Johnson-TL00F, Potter-AL00C, Potter-AL10A, VOGUE-AL00A, VOGUE-AL00A-PRELOAD, VOGUE-AL10C, VOGUE-AL10C-PRELOAD, VOGUE-LGRP1-CHN, VOGUE-LGRP2-OVS, VOGUE-TL00B (medium 5.3)
- [CVE-2019-19412](https://insights.sbomify.com/CVE-2019-19412/): Security feature bypass in ALP-AL00B (medium 4.6)
- [CVE-2018-7901](https://insights.sbomify.com/CVE-2018-7901/): Security feature bypass in ALP-AL00B, BLA-AL00B (medium 4.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-7910 and fix it if it is affected.

What it is: CVE-2018-7910 is a medium-severity authentication bypass vulnerability in Huawei Technologies Co., Ltd. ALP-AL00B, ALP-TL00B, BLA-AL00B, BLA-L09C, BLA-L29C, published on 13 Nov 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-7910 in the wild and no public exploit code.

Affected product: Huawei Technologies Co., Ltd. ALP-AL00B, ALP-TL00B, BLA-AL00B, BLA-L09C, BLA-L29C. 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-7910/ (Markdown: https://insights.sbomify.com/CVE-2018-7910/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-7910
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-7910
- OSV: https://osv.dev/vulnerability/CVE-2018-7910

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-7910/
Summaries are generated and may contain mistakes; the official description above is the record.