# CVE-2020-9235: Information disclosure in HONOR 20 PRO;Honor View 20;OxfordS-AN00A;Princeton-AL10B;Princeton-AL10D;Princeton-TL10C;Tony-AL00B;Yale-AL00A;Yale-L21A;Yale-L61A

> Attackers can exploit a design error in a module to obtain sensitive information, leading to an information leak 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:** 3 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-46w2-3f5r-88m4

## What is CVE-2020-9235?

CVE-2020-9235 is a medium-severity vulnerability in HONOR 20 PRO;Honor View 20;OxfordS-AN00A;Princeton-AL10B;Princeton-AL10D;Princeton-TL10C;Tony-AL00B;Yale-AL00A;Yale-L21A;Yale-L61A, published on 3 Sep 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Huawei smartphones HONOR 20 PRO Versions earlier than 10.1.0.230(C432E9R5P1),Versions earlier than 10.1.0.231(C10E3R3P2),Versions earlier than 10.1.0.231(C185E3R5P1),Versions earlier than 10.1.0.231(C636E3R3P1);Versions earlier than 10.1.0.212(C432E10R3P4),Versions earlier than 10.1.0.213(C636E3R4P3),Versions earlier than 10.1.0.214(C10E5R4P3),Versions earlier than 10.1.0.214(C185E3R3P3);Versions earlier than 10.1.0.212(C00E210R5P1);Versions earlier than 10.1.0.160(C00E160R2P11);Versions earlier than 10.1.0.160(C00E160R2P11);Versions earlier than 10.1.0.160(C01E160R2P11);Versions earlier than 10.1.0.160(C00E160R2P11);Versions earlier than 10.1.0.160(C00E160R8P12);Versions earlier than 10.1.0.230(C432E9R5P1),Versions earlier than 10.1.0.231(C10E3R3P2),Versions earlier than 10.1.0.231(C636E3R3P1);Versions earlier than 10.1.0.225(C431E3R1P2),Versions earlier than 10.1.0.225(C432E3R1P2) contain an information vulnerability. A module has a design error that is lack of control of input. Attackers can exploit this vulnerability to obtain some information. This can lead to information leak.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 10 products.


Products: Huawei Honor 20 Pro Firmware, Huawei Honor View 20 Firmware, Huawei Oxfords-An00a Firmware, Huawei Princeton-Al10b Firmware, Huawei Princeton-Al10d Firmware, Huawei Princeton-Tl10c Firmware, Huawei Tony-Al00b Firmware, Huawei Yale-Al00a Firmware, Huawei Yale-L21a Firmware, Huawei Yale-L61a Firmware.

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

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

## Is CVE-2020-9235 being exploited?

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

## Other vulnerabilities in HONOR 20 PRO;Honor View 20;OxfordS-AN00A;Princeton-AL10B;Princeton-AL10D;Princeton-TL10C;Tony-AL00B;Yale-AL00A;Yale-L21A;Yale-L61A

- [CVE-2020-9223](https://insights.sbomify.com/CVE-2020-9223/): Denial of service in HONOR 20 PRO (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-9235 is a medium-severity vulnerability in HONOR 20 PRO;Honor View 20;OxfordS-AN00A;Princeton-AL10B;Princeton-AL10D;Princeton-TL10C;Tony-AL00B;Yale-AL00A;Yale-L21A;Yale-L61A, published on 3 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-9235 in the wild and no public exploit code.

Affected product: HONOR 20 PRO;Honor View 20;OxfordS-AN00A;Princeton-AL10B;Princeton-AL10D;Princeton-TL10C;Tony-AL00B;Yale-AL00A;Yale-L21A;Yale-L61A. 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-9235/ (Markdown: https://insights.sbomify.com/CVE-2020-9235/index.md)
```

## Sources

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

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