# CVE-2020-14117: Missing authorization in Xiaomi Content Center APP

> Attackers can invoke sensitive component functions in the Xiaomi Content Center app due to missing permission verification, bypassing intended security controls.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Apr 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-vh3x-qhh3-9frg

## What is CVE-2020-14117?

CVE-2020-14117 is a medium-severity missing authorization vulnerability in Xiaomi Content Center APP, published on 21 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A improper permission configuration vulnerability in Xiaomi Content Center APP. This vulnerability is caused by the lack of correct permission verification in the Xiaomi content center APP, and attackers can use this vulnerability to invoke the sensitive component functions of the Xiaomi content center APP.

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

It affects 1 product.


Products: Mi Content Center.

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

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

## Is CVE-2020-14117 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-14117 is a medium-severity missing authorization vulnerability in Xiaomi Content Center APP, published on 21 Apr 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-14117 in the wild and no public exploit code.

Affected product: Xiaomi Content Center APP. 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-14117/ (Markdown: https://insights.sbomify.com/CVE-2020-14117/index.md)
```

## Sources

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

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