# CVE-2019-5281: Information disclosure in Huawei Y9 2019

> A local attacker can exploit a camera vulnerability on Huawei phones to obtain sensitive information through specific operations.

- **Severity:** Medium 4.6 (`CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 4 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-h3vq-5jgm-fc6c

## What is CVE-2019-5281?

CVE-2019-5281 is a medium-severity vulnerability in Huawei Y9 2019, published on 4 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

There is an information leak vulnerability in some Huawei phones, versions earlier than Jackman-L21 8.2.0.155(C185R1P2). When a local attacker uses the camera of a smartphone, the attacker can exploit this vulnerability to obtain sensitive information by performing a series of operations.

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

It affects 1 product.


Products: Huawei Y9 2019 Firmware.

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

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

## Is CVE-2019-5281 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-5281 is a medium-severity vulnerability in Huawei Y9 2019, published on 4 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-5281 in the wild and no public exploit code.

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

## Sources

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

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