# CVE-2019-5299: Security feature bypass in Hima-AL00B

> Attackers can bypass signature verification to install malicious apps that execute arbitrary code on Huawei mobile phones.

- **Severity:** High 7.8 (`CVSS:3.0/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:** 13 Aug 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-r6gh-rc9c-ppvr

## What is CVE-2019-5299?

CVE-2019-5299 is a high-severity vulnerability in Huawei Hima-AL00B, published on 13 Aug 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

Huawei mobile phones Hima-AL00Bhave with Versions earlier than HMA-AL00C00B175 have a signature verification bypass vulnerability. Attackers can induce users to install malicious applications. Due to a defect in the signature verification logic, the malicious applications can invoke specific interface to execute malicious code. A successful exploit may result in the execution of arbitrary code.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

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

It affects 1 product.


Products: Huawei Hima-Al00b Firmware.

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

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

## Is CVE-2019-5299 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-5299 is a high-severity vulnerability in Huawei Hima-AL00B, published on 13 Aug 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-5299 in the wild and no public exploit code.

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

## Sources

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

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