# CVE-2020-1878: Auth bypass in OxfordS-AN00A

> Attackers can load malicious applications to bypass authentication and leak information from Huawei OxfordS-AN00A 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:** 20 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-fwp9-f5c7-pvgj

## What is CVE-2020-1878?

CVE-2020-1878 is a medium-severity authentication bypass vulnerability in OxfordS-AN00A, 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

Huawei smartphone OxfordS-AN00A with versions earlier than 10.0.1.152D(C735E152R3P3),versions earlier than 10.0.1.160(C00E160R4P1) have an improper authentication vulnerability. Authentication to target component is improper when device performs an operation. Attackers exploit this vulnerability to obtain some information by loading malicious application, leading to information leak.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Huawei Oxfords-An00a Firmware.

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

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

## Is CVE-2020-1878 being exploited?

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

## Other vulnerabilities in OxfordS-AN00A

- [CVE-2021-22400](https://insights.sbomify.com/CVE-2021-22400/): Denial of service in OxfordS-AN00A (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-1878 is a medium-severity authentication bypass vulnerability in OxfordS-AN00A, 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-1878 in the wild and no public exploit code.

Affected product: OxfordS-AN00A. 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-1878/ (Markdown: https://insights.sbomify.com/CVE-2020-1878/index.md)
```

## Sources

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

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