# CVE-2019-5297: Security feature bypass in Emily-L29C

> Attackers can bypass Factory Reset Protection on Huawei phones to gain unauthorized access to the device after a reset.

- **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:** 4 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-x6xf-9vgf-7wgc

## What is CVE-2019-5297?

CVE-2019-5297 is a medium-severity vulnerability in Huawei Emily-L29C, published on 4 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Emily-L29C Huawei phones versions earlier than 9.0.0.159 (C185E2R1P12T8) have a Factory Reset Protection (FRP) bypass security vulnerability. Before the FRP account is verified and activated during the reset process, the attacker can perform some special operations to bypass the FRP function and obtain the right to use the mobile phone.

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

It affects 1 product.


Products: Huawei Emily-L29c Firmware.

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

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

## Is CVE-2019-5297 being exploited?

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

## Other vulnerabilities in Huawei Emily-L29C

- [CVE-2019-5236](https://insights.sbomify.com/CVE-2019-5236/): Use after free in Emily-L29C (medium 6.3)
- [CVE-2019-5279](https://insights.sbomify.com/CVE-2019-5279/): Information disclosure in Emily-L29C (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-5297 and fix it if it is affected.

What it is: CVE-2019-5297 is a medium-severity vulnerability in Huawei Emily-L29C, published on 4 Jun 2019. 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-5297 in the wild and no public exploit code.

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

## Sources

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

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