# CVE-2019-5282: Use after free in Emily-AL00A, Emily-TL00B, Emily-L09C, Emily-L29C

> A double free vulnerability in the Bastet module allows attackers to execute malicious code by tricking users into installing a malicious application.

- **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:** 13 Nov 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-38wh-jw2h-h2f5

## What is CVE-2019-5282?

CVE-2019-5282 is a high-severity use after free vulnerability in Emily-AL00A, Emily-TL00B, Emily-L09C, Emily-L29C, published on 13 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

Bastet module of some Huawei smartphones with Versions earlier than Emily-AL00A 9.0.0.182(C00E82R1P21), Versions earlier than Emily-TL00B 9.0.0.182(C01E82R1P21), Versions earlier than Emily-L09C 9.0.0.203(C432E7R1P11), Versions earlier than Emily-L29C 9.0.0.203(C432E7R1P11), Versions earlier than Emily-L29C 9.0.0.202(C185E2R1P12) have a double free vulnerability. An attacker tricks the user into installing a malicious application, which frees on the same memory address twice. Successful exploit could result in malicious code execution.

Weakness: CWE-415 (Double Free)

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

It affects 7 products.


Products: Huawei Emily-Al00a Firmware, Huawei Emily-L09c Firmware, Huawei Emily-L29c Firmware, Huawei Emily-Tl00b Firmware, Huawei Hima-L09ca Firmware, Huawei Hima-L29c Firmware, Huawei Hima-L29ca Firmware.

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

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

## Is CVE-2019-5282 being exploited?

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

## Other vulnerabilities in Emily-AL00A, Emily-TL00B, Emily-L09C, Emily-L29C

- [CVE-2018-7925](https://insights.sbomify.com/CVE-2018-7925/): Auth bypass in Emily-AL00A (medium 6.8)
- [CVE-2018-7944](https://insights.sbomify.com/CVE-2018-7944/): Security feature bypass in Emily-AL00A (medium 6.8)
- [CVE-2018-7961](https://insights.sbomify.com/CVE-2018-7961/): Information disclosure in Emily-AL00A (medium 6.5)
- [CVE-2018-7947](https://insights.sbomify.com/CVE-2018-7947/): Auth bypass in Emily-AL00A (low 3.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-5282 is a high-severity use after free vulnerability in Emily-AL00A, Emily-TL00B, Emily-L09C, Emily-L29C, published on 13 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-5282 in the wild and no public exploit code.

Affected product: Emily-AL00A, Emily-TL00B, Emily-L09C, Emily-L29C. 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-5282/ (Markdown: https://insights.sbomify.com/CVE-2019-5282/index.md)
```

## Sources

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

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