# CVE-2020-14112: Information disclosure in Router AX6000

> Attackers can download files from the Xiaomi Router AX6000 due to incorrect routing configuration, leading to information disclosure.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Mar 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2w73-w3hw-6wpj

## What is CVE-2020-14112?

CVE-2020-14112 is a medium-severity vulnerability in Router AX6000, published on 7 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Information Leak Vulnerability exists in the Xiaomi Router AX6000. The vulnerability is caused by incorrect routing configuration. Attackers can exploit this vulnerability to download part of the files in Xiaomi Router AX6000.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Mi Ax6000 Firmware.

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

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

## Is CVE-2020-14112 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-14112 is a medium-severity vulnerability in Router AX6000, published on 7 Mar 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-14112 in the wild and no public exploit code.

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

## Sources

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

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