# CVE-2019-19412: Security feature bypass in ALP-AL00B

> Attackers can bypass Factory Reset Protection on Huawei smartphones via Talkback mode to install unauthorized third-party applications.

- **Severity:** Medium 4.6 (`CVSS:3.1/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:** 8 Jun 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-gvv5-wgp2-xf56

## What is CVE-2019-19412?

CVE-2019-19412 is a medium-severity vulnerability in Huawei ALP-AL00B, published on 8 Jun 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Huawei smart phones have a Factory Reset Protection (FRP) bypass security vulnerability. When re-configuring the mobile phone using the factory reset protection (FRP) function, an attacker login the Talkback mode and can perform some operations to install a third-Party application. Affected products can be found in https://www.huawei.com/en/psirt/security-advisories/huawei-sa-20200115-01-frp-en.

## Which versions are affected by CVE-2019-19412?

It affects 28 products.


Products: Huawei Alp-Al00b Firmware, Huawei Alp-L09 Firmware, Huawei Alp-L29 Firmware, Huawei Anne-Al00 Firmware, Huawei Berkeley-Al20 Firmware, Huawei Berkeley-L09 Firmware, Huawei Bla-Al00b Firmware, Huawei Bla-L09c Firmware, Huawei Bla-L29c Firmware, Huawei Emily-L29c Firmware, Huawei Figo-L03 Firmware, Huawei Figo-L21 Firmware, Huawei Figo-L23 Firmware, Huawei Figo-L31 Firmware, Huawei Florida-L03 Firmware, Huawei Florida-L21 Firmware, Huawei Florida-L22 Firmware, Huawei Florida-L23 Firmware, Huawei Honor View 10 Firmware, Huawei Leland-Al00a Firmware and 8 more.

## How do I fix CVE-2019-19412?

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

## Is CVE-2019-19412 being exploited?

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

## Other vulnerabilities in Huawei ALP-AL00B

- [CVE-2018-7910](https://insights.sbomify.com/CVE-2018-7910/): Auth bypass in ALP-AL00B, ALP-TL00B, BLA-AL00B, BLA-L09C, BLA-L29C (medium 6.8)
- [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-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-2019-19412 and fix it if it is affected.

What it is: CVE-2019-19412 is a medium-severity vulnerability in Huawei ALP-AL00B, published on 8 Jun 2020. 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-2019-19412 in the wild and no public exploit code.

Affected product: Huawei ALP-AL00B. 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-2019-19412/ (Markdown: https://insights.sbomify.com/CVE-2019-19412/index.md)
```

## Sources

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

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