# CVE-2020-9244: Auth bypass in HUAWEI Mate 20;HUAWEI Mate 20 Pro;HUAWEI Mate 20 X;HUAWEI P30;HUAWEI P30 Pro;HUAWEI Mate 20 RS;HonorMagic2;Honor20;Honor20 PRO;HonorMagic2;HonorV20

> Attackers can forge encrypted files by exploiting improper authentication in Huawei mobile devices, requiring key acquisition.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-jx8x-69j8-c7fj

## What is CVE-2020-9244?

CVE-2020-9244 is a medium-severity authentication bypass vulnerability in HUAWEI Mate 20;HUAWEI Mate 20 Pro;HUAWEI Mate 20 X;HUAWEI P30;HUAWEI P30 Pro;HUAWEI Mate 20 RS;HonorMagic2;Honor20;Honor20 PRO;HonorMagic2;HonorV20, published on 11 Aug 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

HUAWEI Mate 20 versions Versions earlier than 10.1.0.160(C00E160R3P8);HUAWEI Mate 20 Pro versions Versions earlier than 10.1.0.270(C431E7R1P5),Versions earlier than 10.1.0.270(C635E3R1P5),Versions earlier than 10.1.0.273(C636E7R2P4);HUAWEI Mate 20 X versions Versions earlier than 10.1.0.160(C00E160R2P8);HUAWEI P30 versions Versions earlier than 10.1.0.160(C00E160R2P11);HUAWEI P30 Pro versions Versions earlier than 10.1.0.160(C00E160R2P8);HUAWEI Mate 20 RS versions Versions earlier than 10.1.0.160(C786E160R3P8);HonorMagic2 versions Versions earlier than 10.0.0.187(C00E61R2P11);Honor20 versions Versions earlier than 10.0.0.175(C00E58R4P11);Honor20 PRO versions Versions earlier than 10.0.0.194(C00E62R8P12);HonorMagic2 versions Versions earlier than 10.0.0.187(C00E61R2P11);HonorV20 versions Versions earlier than 10.0.0.188(C00E62R2P11) have an improper authentication vulnerability. The system does not properly sign certain encrypted file, the attacker should gain the key used to encrypt the file, successful exploit could cause certain file be forged

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

It affects 10 products.


Products: Huawei Honor 20 Firmware, Huawei Honor 20 Pro Firmware, Huawei Honor Magic 2 Firmware, Huawei Honor V20 Firmware, Huawei Mate 20 Firmware, Huawei Mate 20 Pro Firmware, Huawei Mate 20 Rs Firmware, Huawei Mate 20 X Firmware, Huawei P30 Firmware, Huawei P30 Pro Firmware.

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

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

## Is CVE-2020-9244 being exploited?

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

## Other vulnerabilities in HUAWEI Mate 20;HUAWEI Mate 20 Pro;HUAWEI Mate 20 X;HUAWEI P30;HUAWEI P30 Pro;HUAWEI Mate 20 RS;HonorMagic2;Honor20;Honor20 PRO;HonorMagic2;HonorV20

- [CVE-2020-1808](https://insights.sbomify.com/CVE-2020-1808/): Information disclosure in Honor 20;HONOR 20 PRO;Honor Magic2;HUAWEI Mate 20 X;HUAWEI P30;HUAWEI P30 Pro;Honor View 20 (high 7.1)
- [CVE-2020-9074](https://insights.sbomify.com/CVE-2020-9074/): Denial of service in HONOR 20 (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-9244 is a medium-severity authentication bypass vulnerability in HUAWEI Mate 20;HUAWEI Mate 20 Pro;HUAWEI Mate 20 X;HUAWEI P30;HUAWEI P30 Pro;HUAWEI Mate 20 RS;HonorMagic2;Honor20;Honor20 PRO;HonorMagic2;HonorV20, published on 11 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-9244 in the wild and no public exploit code.

Affected product: HUAWEI Mate 20;HUAWEI Mate 20 Pro;HUAWEI Mate 20 X;HUAWEI P30;HUAWEI P30 Pro;HUAWEI Mate 20 RS;HonorMagic2;Honor20;Honor20 PRO;HonorMagic2;HonorV20. 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-9244/ (Markdown: https://insights.sbomify.com/CVE-2020-9244/index.md)
```

## Sources

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

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