# CVE-2020-9239: Information disclosure in BLA-A09;BLA-TL00B;Berkeley-L09;Duke-L09;HUAWEI P20;HUAWEI P20 Pro;Jimmy-AL00A;LON-L29D;NEO-AL00D;Stanford-AL00;Toronto-AL00;Toronto-AL00A;Toronto-TL10

> Attackers can exploit a design error in a module lacking input control to disclose information on affected Huawei smartphones.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 11 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-f8jg-xpjx-j54w

## What is CVE-2020-9239?

CVE-2020-9239 is a medium-severity vulnerability in BLA-A09;BLA-TL00B;Berkeley-L09;Duke-L09;HUAWEI P20;HUAWEI P20 Pro;Jimmy-AL00A;LON-L29D;NEO-AL00D;Stanford-AL00;Toronto-AL00;Toronto-AL00A;Toronto-TL10, published on 11 Sep 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Huawei smartphones BLA-A09 versions 8.0.0.123(C212),versions earlier than 8.0.0.123(C567),versions earlier than 8.0.0.123(C797);BLA-TL00B versions earlier than 8.1.0.326(C01);Berkeley-L09 versions earlier than 8.0.0.163(C10),versions earlier than 8.0.0.163(C432),Versions earlier than 8.0.0.163(C636),Versions earlier than 8.0.0.172(C10);Duke-L09 versions Duke-L09C10B187, versions Duke-L09C432B189, versions Duke-L09C636B189;HUAWEI P20 versions earlier than 8.0.1.16(C00);HUAWEI P20 Pro versions earlier than 8.1.0.152(C00);Jimmy-AL00A versions earlier than Jimmy-AL00AC00B172;LON-L29D versions LON-L29DC721B192;NEO-AL00D versions earlier than 8.1.0.172(C786);Stanford-AL00 versions Stanford-AL00C00B123;Toronto-AL00 versions earlier than Toronto-AL00AC00B225;Toronto-AL00A versions earlier than Toronto-AL00AC00B225;Toronto-TL10 versions earlier than Toronto-TL10C01B225 have an information vulnerability. A module has a design error that is lack of control of input. Attackers can exploit this vulnerab

Weakness: CWE-20 (Improper Input Validation)

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

It affects 13 products.


Products: Huawei Berkeley-L09 Firmware, Huawei Bla-A09 Firmware, Huawei Bla-Tl00b Firmware, Huawei Duke-L09 Firmware, Huawei Jimmy-Al00a Firmware, Huawei Lon-L29d Firmware, Huawei Neo-Al00d Firmware, Huawei P20 Firmware, Huawei P20 Pro Firmware, Huawei Stanford-Al00 Firmware, Huawei Toronto-Al00 Firmware, Huawei Toronto-Al00a Firmware, Huawei Toronto-Tl10 Firmware.

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

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

## Is CVE-2020-9239 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-9239 is a medium-severity vulnerability in BLA-A09;BLA-TL00B;Berkeley-L09;Duke-L09;HUAWEI P20;HUAWEI P20 Pro;Jimmy-AL00A;LON-L29D;NEO-AL00D;Stanford-AL00;Toronto-AL00;Toronto-AL00A;Toronto-TL10, published on 11 Sep 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-9239 in the wild and no public exploit code.

Affected product: BLA-A09;BLA-TL00B;Berkeley-L09;Duke-L09;HUAWEI P20;HUAWEI P20 Pro;Jimmy-AL00A;LON-L29D;NEO-AL00D;Stanford-AL00;Toronto-AL00;Toronto-AL00A;Toronto-TL10. 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-9239/ (Markdown: https://insights.sbomify.com/CVE-2020-9239/index.md)
```

## Sources

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

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