Unauthenticated container access via wildcard port binding
Published May 24, 2023 · Updated Jan 16, 2025
Incorrect privilege assignment in Kubernetes minikube 1.26.0 through 1.28.0 allows remote attackers to access its container. On macOS, the Docker driver publishes the container’s 8443/tcp mapping on 0.0.0.0 instead of restricting HostIp to 127.0.0.1. The affected cluster must use the Docker driver, and the wildcard binding makes the container reachable from networks outside the host.
Summary
What happened
Incorrect privilege assignment in Kubernetes minikube 1.26.0 through 1.28.0 allows remote attackers to access its container. On macOS, the Docker driver publishes the container’s 8443/tcp mapping on 0.0.0.0 instead of restricting HostIp to 127.0.0.1. The affected cluster must use the Docker driver, and the wildcard binding makes the container reachable from networks outside the host.
The record
- CVE
- CVE-2023-1174
- Published
- May 24, 2023
- Updated
- Jan 16, 2025
- Vendor
- Kubernetes
- Product
- minikube
- Classifications
- CWE-266, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 24, 2023CVE publishedPublication date reported by the CVE source.
- Jan 16, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.26.0 <unspecified
- Affected versionversion=unspecified <=1.28.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo