# CVE-2019-18371: Path traversal in n/a

> Attackers can read arbitrary files and bypass authentication on Xiaomi Mi WiFi R3G routers via a directory traversal vulnerability in NGINX configuration.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 23 Oct 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-6h3g-375j-8gv3

## What is CVE-2019-18371?

CVE-2019-18371 is a high-severity path traversal vulnerability in n/a, published on 23 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on Xiaomi Mi WiFi R3G devices before 2.28.23-stable. There is a directory traversal vulnerability to read arbitrary files via a misconfigured NGINX alias, as demonstrated by api-third-party/download/extdisks../etc/config/account. With this vulnerability, the attacker can bypass authentication.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2019-18371?

It affects 1 product.


Products: Mi Millet Router 3g Firmware.

## How do I fix CVE-2019-18371?

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

## Is CVE-2019-18371 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-18371 exists.

Public exploit code:

- A login bypass(CVE-2019-18371) and a command injection vulnerability(CVE-2019-18370) in Xiaomi Router R3G up to version 2.28.23. (github_poc): https://github.com/UltramanGaia/Xiaomi_Mi_WiFi_R3G_Vulnerability_POC
- A login bypass(CVE-2019-18371) and a command injection vulnerability(CVE-2019-18370) in Xiaomi Router R3G up to versi… (github_poc): https://github.com/AjayMT6/UltramanGaia
- Xiaomi Mi WiFi R3G Routers - Local file Inclusion (nuclei): http/cves/2019/CVE-2019-18371.yaml

## Other vulnerabilities in n/a

- [CVE-2019-18370](https://insights.sbomify.com/CVE-2019-18370/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-18371 and fix it if it is affected.

What it is: CVE-2019-18371 is a high-severity path traversal vulnerability in n/a, published on 23 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-18371 exists.

Affected product: n/a. 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-2019-18371/ (Markdown: https://insights.sbomify.com/CVE-2019-18371/index.md)
```

## Sources

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

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