[minikube] Network Port exposure in minikube running on macOS using Docker driver
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Kubernetes | minikube | affected |
|
Configuration 1 [-]
| AND |
|
No data.
No data available yet.
Vendor Solution
To mitigate these vulnerabilities, upgrade minikube to the latest version and delete any clusters created using an affected version. To delete clusters created using prior versions, run `minikube delete --all`
Vendor Workaround
To continue using an existing cluster, change the default port mappings of the minikube container and restart the docker daemon - docker run -v /var/lib/docker:/var/lib/docker -e MINIKUBE_CONTAINER_ID="$(docker ps --no-trunc -aqf 'name=^minikube$')" -it --entrypoint /bin/sh alpine sed -i 's/0.0.0.0/127.0.0.1/g' /var/lib/docker/containers/$MINIKUBE_CONTAINER_ID/config.v2.json
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2023-23456 | This vulnerability exposes a network port in minikube running on macOS with Docker driver that could enable unexpected remote access to the minikube container. |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.756% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|