# CVE-2019-5252: Auth bypass in Y9, Honor 8X, Honor 9 Lite, Honor 9i, Y6 Pro

> Attackers can bypass applock authentication on specific Huawei smartphones to access locked applications instantly.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:L/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:** 13 Dec 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-252p-r436-cv4f

## What is CVE-2019-5252?

CVE-2019-5252 is a low-severity authentication bypass vulnerability in Y9, Honor 8X, Honor 9 Lite, Honor 9i, Y6 Pro, published on 13 Dec 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

There is an improper authentication vulnerability in Huawei smartphones (Y9, Honor 8X, Honor 9 Lite, Honor 9i, Y6 Pro). The applock does not perform a sufficient authentication in a rare condition. Successful exploit could allow the attacker to use the application locked by applock in an instant.

Weakness: CWE-287 (Improper Authentication)

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

It affects 6 products.


Products: Huawei Enjoy 8 Plus Firmware, Huawei Honor 8x Firmware, Huawei Honor 9 Lite Firmware, Huawei Honor 9i Firmware, Huawei Y6 Pro Firmware, Huawei Y9 Firmware.

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

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

## Is CVE-2019-5252 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-5252 is a low-severity authentication bypass vulnerability in Y9, Honor 8X, Honor 9 Lite, Honor 9i, Y6 Pro, published on 13 Dec 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-5252 in the wild and no public exploit code.

Affected product: Y9, Honor 8X, Honor 9 Lite, Honor 9i, Y6 Pro. 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-5252/ (Markdown: https://insights.sbomify.com/CVE-2019-5252/index.md)
```

## Sources

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

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