# CVE-2019-5295: Auth bypass in Honor V10

> Attackers can bypass authorization scopes on Huawei Honor V10 devices to perform unauthorized operations due to improper implementation logic.

- **Severity:** Medium 6.4 (`CVSS:3.0/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 6 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-m4jg-hxh8-hp87

## What is CVE-2019-5295?

CVE-2019-5295 is a medium-severity authentication bypass vulnerability in Huawei Honor V10, published on 6 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Huawei Honor V10 smartphones versions earlier than Berkeley-AL20 9.0.0.125(C00E125R2P14T8) have an authorization bypass vulnerability. Due to improper authorization implementation logic, attackers can bypass certain authorization scopes of smart phones by performing specific operations. This vulnerability can be exploited to perform operations beyond the scope of authorization.

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

It affects 1 product.


Products: Huawei Honor View 10 Firmware.

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

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

## Is CVE-2019-5295 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-5295 is a medium-severity authentication bypass vulnerability in Huawei Honor V10, published on 6 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-5295 in the wild and no public exploit code.

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

## Sources

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

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