# CVE-2019-5213: Auth bypass in Honor play

> Attackers can bypass screen lock to modify alarm settings on Honor Play devices via a logic error, requiring a firmware update.

- **Severity:** Low 2.4 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/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:** 12 Nov 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-r76g-8cjw-fqwr

## What is CVE-2019-5213?

CVE-2019-5213 is a low-severity authentication bypass vulnerability in Honor play, published on 12 Nov 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Honor play smartphones with versions earlier than Cornell-AL00A 9.1.0.321(C00E320R1P1T8) have an insufficient authentication vulnerability. The system has a logic judge error under certain scenario. Successful exploit could allow the attacker to modify the alarm clock settings after a serious of uncommon operations without unlock the screen lock.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Huawei Honor Play Firmware.

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

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

## Is CVE-2019-5213 being exploited?

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

## Other vulnerabilities in Honor play

- [CVE-2019-5309](https://insights.sbomify.com/CVE-2019-5309/): Information disclosure in Honor play (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-5213 is a low-severity authentication bypass vulnerability in Honor play, published on 12 Nov 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-5213 in the wild and no public exploit code.

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

## Sources

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

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