# CVE-2020-1833: Auth bypass in Honor 9X

> Attackers can bypass lock screen authentication to access clock information on Honor 9X devices via a logic error in the clock function.

- **Severity:** Low 2.4 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/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:** 29 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-fhq2-85vv-r2h7

## What is CVE-2020-1833?

CVE-2020-1833 is a low-severity authentication bypass vulnerability in Huawei Honor 9X, published on 29 May 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Honor 9X smartphones with versions earlier than 9.1.1.172(C00E170R8P1) have an improper authentication vulnerability. A logic error occurs when handling clock function, an attacker should do a series of crafted operations quickly before the phone is unlocked, successful exploit could allow the attacker to access clock information without unlock the phone.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Huawei Honor 9x Firmware.

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

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

## Is CVE-2020-1833 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-1833 is a low-severity authentication bypass vulnerability in Huawei Honor 9X, published on 29 May 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-1833 in the wild and no public exploit code.

Affected product: Huawei Honor 9X. 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-1833/ (Markdown: https://insights.sbomify.com/CVE-2020-1833/index.md)
```

## Sources

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

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