# CVE-2018-1002103: Minikube RCE via DNS Rebinding

> Attackers can use DNS rebinding to access the Kubernetes Dashboard and execute arbitrary code or read host files in predictable VM environments.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Dec 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-6pcv-qqx4-mxm3, GO-2023-1961, openSUSE-SU-2024:11051-1

## What is CVE-2018-1002103?

CVE-2018-1002103 is a high-severity vulnerability in Kubernetes Minikube, published on 5 Dec 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

In Minikube versions 0.3.0-0.29.0, minikube exposes the Kubernetes Dashboard listening on the VM IP at port 30000. In VM environments where the IP is easy to predict, the attacker can use DNS rebinding to indirectly make requests to the Kubernetes Dashboard, create a new Kubernetes Deployment running arbitrary code. If minikube mount is in use, the attacker could also directly access the host filesystem.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

3 open source packages ship an affected version, including k8s.io/minikube. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `k8s.io/minikube` | Go | From 0.3.0 | None |
| `k8s.io/minikube` | Go | From 0.3.0 to 0.29.0 | None |
| `k8s.io/minikube` | Go | From 0.3.0 to 0.29.0 | None |

Products: Kubernetes Minikube.

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

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

## Is CVE-2018-1002103 being exploited?

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

## Other vulnerabilities in Kubernetes Minikube

- [CVE-2023-1174](https://insights.sbomify.com/CVE-2023-1174/): [minikube] Network Port exposure in minikube running on macOS using Docker driver (critical 9.8)
- [CVE-2023-1944](https://insights.sbomify.com/CVE-2023-1944/): [minikube] ssh server with default password (high 8.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-1002103 is a high-severity vulnerability in Kubernetes Minikube, published on 5 Dec 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-1002103 in the wild and no public exploit code.

Affected packages and fixed versions:
- k8s.io/minikube (Go): affected from 0.3.0; no fix listed
- k8s.io/minikube (Go): affected from 0.3.0 up to 0.29.0; no fix listed
- k8s.io/minikube (Go): affected from 0.3.0 up to 0.29.0; no fix listed

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

## Sources

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

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