# CVE-2020-14131: Other in Xiaomi specific devices

> The provided text is a generic acknowledgment from Xiaomi Security Center and lacks specific technical details regarding the vulnerability's nature or impact.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Oct 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-wvmm-9g2m-qqr7

## What is CVE-2020-14131?

CVE-2020-14131 is a critical vulnerability in Xiaomi specific devices, published on 11 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Xiaomi Security Center expresses heartfelt thanks to ADLab of VenusTech ! At the same time, we also welcome more outstanding and professional security experts and security teams to join the Mi Security Center (MiSRC) to jointly ensure the safe access of millions of Xiaomi users worldwide Life.

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

It affects 1 product.


Products: Mi Xiaomi.

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

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

## Is CVE-2020-14131 being exploited?

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

## Other vulnerabilities in Xiaomi specific devices

- [CVE-2020-14129](https://insights.sbomify.com/CVE-2020-14129/): Auth bypass in Xiaomi a certain APP (critical 9.8)
- [CVE-2020-14130](https://insights.sbomify.com/CVE-2020-14130/): Missing authorization in Xiaomi community app (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-14131 is a critical vulnerability in Xiaomi specific devices, published on 11 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-14131 in the wild and no public exploit code.

Affected product: Xiaomi specific devices. 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-14131/ (Markdown: https://insights.sbomify.com/CVE-2020-14131/index.md)
```

## Sources

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

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