MinikubeApplication · Kubernetes
CVE-2018-1002103
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMinikube 0.3.0-0.29.0 exposes the Kubernetes Dashboard on the VM IP at port 30000 with no authentication. This predictable network location enables DNS rebinding attacks where an attacker tricks a browser into making requests to the dashboard, potentially creating Kubernetes Deployments to execute arbitrary code. When minikube mount is active, the attacker can also directly read/write to the host filesystem via the exposed mount.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
MinikubeApplication
>= 0.3.0, <= 0.29.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Minikube versionRun 'minikube version' to retrieve the version numberAffected if The version is >= 0.3.0 and <= 0.29.0
-
Verify Kubernetes Dashboard is accessible on port 30000Run 'minikube status' to get the VM IP, then attempt to access http://<VM-IP>:30000 in a browser or via curlAffected if The Dashboard loads without requiring authentication credentials
-
Check if port 30000 is listening on the Minikube VMRun 'minikube ssh' and then 'netstat -tlnp | grep 30000' or 'ss -tlnp | grep 30000' inside the Minikube VMAffected if Port 30000 is bound and listening
-
Determine network exposure of port 30000Check host firewall rules or network configuration to see if port 30000 is accessible from external addresses, or test from another machine on the networkAffected if Port 30000 is accessible from network addresses other than localhost
-
Check if Minikube mount is activeRun 'minikube mount' to see if any mount configurations are activeAffected if A Minikube mount is currently active and port 30000 is network-accessible
You are affected if your Minikube version is between 0.3.0 and 0.29.0 AND the Kubernetes Dashboard on port 30000 is accessible without authentication from your local machine or network.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Minikube to version 0.30.0 or later, which addresses the exposure. Alternatively, configure host-level firewall rules to block external access to port 30000.
Fix this in Minikube
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1002103 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-1002103 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data