# CVE-2018-16307: Server-side request forgery in n/a

> Attackers can force the router to fetch arbitrary external URLs and return their contents, enabling Server-Side Request Forgery and data exfiltration.

- **Severity:** High 7.5 (`CVSS:3.0/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:** 5 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-q6h6-wxwc-jw35

## What is CVE-2018-16307?

CVE-2018-16307 is a high-severity server-side request forgery vulnerability in n/a, published on 5 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An "Out-of-band resource load" issue was discovered on Xiaomi MIWiFi Xiaomi_55DD Version 2.8.50 devices. It is possible to induce the application to retrieve the contents of an arbitrary external URL and return those contents in its own response. If a domain name (containing a random string) is used in the HTTP Host header, the application performs an HTTP request to the specified domain. The response from that request is then included in the application's own response.

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

## Which versions are affected by CVE-2018-16307?

It affects 1 product.


Products: Mi Xiaomi Miwifi Xiaomi 55dd Firmware.

## How do I fix CVE-2018-16307?

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

## Is CVE-2018-16307 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-16307 and fix it if it is affected.

What it is: CVE-2018-16307 is a high-severity server-side request forgery vulnerability in n/a, published on 5 Sep 2018. 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-2018-16307 in the wild and no public exploit code.

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-2018-16307/ (Markdown: https://insights.sbomify.com/CVE-2018-16307/index.md)
```

## Sources

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

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