# CVE-2020-1792: Memory corruption in Honor V10

> A malicious application can trigger an out-of-bounds write in the Honor V10 driver, causing the device to reboot.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Feb 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-838v-88q9-7fmf

## What is CVE-2020-1792?

CVE-2020-1792 is a medium-severity memory corruption vulnerability in Honor V10, published on 28 Feb 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Honor V10 smartphones with versions earlier than BKL-AL20 10.0.0.156(C00E156R2P4) and versions earlier than BKL-L09 10.0.0.146(C432E4R1P4) have an out of bounds write vulnerability. The software writes data past the end of the intended buffer because of insufficient validation of certain parameter when initializing certain driver program. An attacker could trick the user into installing a malicious application, successful exploit could cause the device to reboot.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2020-1792?

It affects 1 product.


Products: Huawei Honor V10 Firmware.

## How do I fix CVE-2020-1792?

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

## Is CVE-2020-1792 being exploited?

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

## Other vulnerabilities in Honor V10

- [CVE-2020-1804](https://insights.sbomify.com/CVE-2020-1804/): Information disclosure in Honor V10 (high 7.1)
- [CVE-2020-1805](https://insights.sbomify.com/CVE-2020-1805/): Information disclosure in Honor V10 (high 7.1)
- [CVE-2020-1806](https://insights.sbomify.com/CVE-2020-1806/): Information disclosure in Honor V10 (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-1792 and fix it if it is affected.

What it is: CVE-2020-1792 is a medium-severity memory corruption vulnerability in Honor V10, published on 28 Feb 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-1792 in the wild and no public exploit code.

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

## Sources

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

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