# CVE-2020-1793: Auth bypass in HUAWEI Mate 20;HUAWEI Mate 30 Pro

> Improper authentication in Huawei smartphone applock allows attackers to bypass locks and access protected application data.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 20 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-r7pj-wp43-jmpp

## What is CVE-2020-1793?

CVE-2020-1793 is a medium-severity authentication bypass vulnerability in HUAWEI Mate 20;HUAWEI Mate 30 Pro, published on 20 Mar 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

There is an improper authentication vulnerability in several smartphones. The applock does not perform a sufficient authentication in certain scenarios, successful exploit could allow the attacker to gain certain data of the application which is locked. Affected product versions include:HUAWEI Mate 20 versions Versions earlier than 10.0.0.188(C00E74R3P8);HUAWEI Mate 30 Pro versions Versions earlier than 10.0.0.203(C00E202R7P2).

Weakness: CWE-287 (Improper Authentication)

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

It affects 2 products.


Products: Huawei Mate 20 Firmware, Huawei Mate 30 Pro Firmware.

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

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

## Is CVE-2020-1793 being exploited?

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

## Other vulnerabilities in HUAWEI Mate 20;HUAWEI Mate 30 Pro

- [CVE-2020-9113](https://insights.sbomify.com/CVE-2020-9113/): Memory corruption in HUAWEI Mate 20 (high 8.0)
- [CVE-2019-5225](https://insights.sbomify.com/CVE-2019-5225/): Memory corruption in P30, Mate 20, P30 Pro (high 7.8)
- [CVE-2020-1796](https://insights.sbomify.com/CVE-2020-1796/): Missing authorization in HUAWEI Mate 20;HUAWEI Mate 30 Pro (medium 6.6)
- [CVE-2020-1787](https://insights.sbomify.com/CVE-2020-1787/): Auth bypass in HUAWEI Mate 20 (medium 6.6)
- [CVE-2020-1840](https://insights.sbomify.com/CVE-2020-1840/): Auth bypass in HUAWEI Mate 20 (medium 6.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-1793 is a medium-severity authentication bypass vulnerability in HUAWEI Mate 20;HUAWEI Mate 30 Pro, published on 20 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-1793 in the wild and no public exploit code.

Affected product: HUAWEI Mate 20;HUAWEI Mate 30 Pro. 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-1793/ (Markdown: https://insights.sbomify.com/CVE-2020-1793/index.md)
```

## Sources

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

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