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

> Attackers can cause denial of service on Huawei Taurus-AL00B smartphones by exploiting a use-after-free vulnerability in a module lacking lock protection.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-w7q6-2xg4-7447

## What is CVE-2020-9237?

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

### Official description

Huawei smartphone Taurus-AL00B with versions earlier than 10.1.0.126(C00E125R5P3) have a user after free vulnerability. A module is lack of lock protection. Attackers can exploit this vulnerability by launching specific request. This could compromise normal service of the affected device.

Weakness: CWE-416 (Use After Free)

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

It affects 1 product.


Products: Huawei Taurus-Al00b Firmware.

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

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

## Is CVE-2020-9237 being exploited?

There is no known exploitation of CVE-2020-9237 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-9070](https://insights.sbomify.com/CVE-2020-9070/): Auth bypass in Taurus-AL00B (medium 5.5)
- [CVE-2020-9065](https://insights.sbomify.com/CVE-2020-9065/): Use after free in Taurus-AL00B (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-9237 is a medium-severity use after free vulnerability in Taurus-AL00B, published on 17 Aug 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-9237 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-9237/ (Markdown: https://insights.sbomify.com/CVE-2020-9237/index.md)
```

## Sources

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

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