# CVE-2019-5210: Integer overflow in Nova 5i pro, Nova 5

> Attackers can execute malicious code by tricking users into installing a malicious app that exploits improper array index validation in Huawei Nova devices.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Nov 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-7p23-r8cx-mw8p

## What is CVE-2019-5210?

CVE-2019-5210 is a high-severity vulnerability in Nova 5i pro, Nova 5, published on 29 Nov 2019. 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

Nova 5i pro and Nova 5 smartphones with versions earlier than 9.1.1.190(C00E190R6P2)and Versions earlier than 9.1.1.175(C00E170R3P2) have an improper validation of array index vulnerability. The system does not properly validate the input value before use it as an array index when processing certain image information. The attacker tricks the user into installing a malicious application, successful exploit could cause malicious code execution.

Weakness: CWE-129 (Improper Validation of Array Index)

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

It affects 2 products.


Products: Huawei Nova 5 Firmware, Huawei Nova 5i Pro Firmware.

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

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

## Is CVE-2019-5210 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-5210 is a high-severity vulnerability in Nova 5i pro, Nova 5, published on 29 Nov 2019. 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-2019-5210 in the wild and no public exploit code.

Affected product: Nova 5i pro, Nova 5. 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-5210/ (Markdown: https://insights.sbomify.com/CVE-2019-5210/index.md)
```

## Sources

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

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