# CVE-2020-9065: Use after free in Taurus-AL00B

> A local authenticated attacker can exploit a use-after-free flaw in Huawei smartphones to tamper with information and affect availability.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-qh3h-hjmm-mvg3

## What is CVE-2020-9065?

CVE-2020-9065 is a medium-severity use after free vulnerability in Taurus-AL00B, published on 26 Mar 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Huawei smart phone Taurus-AL00B with versions earlier than 10.0.0.203(C00E201R7P2) have a use-after-free (UAF) vulnerability. An authenticated, local attacker may perform specific operations to exploit this vulnerability. Successful exploitation may tamper with the information to affect the availability.

Weakness: CWE-416 (Use After Free)

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

It affects 1 product.


Products: Huawei Taurus-Al00b Firmware.

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

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

## Is CVE-2020-9065 being exploited?

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

## Other vulnerabilities in Taurus-AL00B

- [CVE-2019-5233](https://insights.sbomify.com/CVE-2019-5233/): Auth bypass in Taurus-AL00B (high 8.8)
- [CVE-2020-9237](https://insights.sbomify.com/CVE-2020-9237/): Use after free in Taurus-AL00B (medium 6.7)
- [CVE-2020-9070](https://insights.sbomify.com/CVE-2020-9070/): Auth bypass in Taurus-AL00B (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-9065 is a medium-severity use after free vulnerability in Taurus-AL00B, published on 26 Mar 2020. 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-2020-9065 in the wild and no public exploit code.

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

## Sources

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

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