CVE-2018-1002105: Critical severity kubernetes dashboard vulnerability
In all Kubernetes versions prior to v1.10.11, v1.11.5, and v1.12.3, incorrect handling of error responses to proxied upgrade requests in the kube-apiserver allowed specially crafted requests to establish a connection through the Kubernetes API server to backend servers, then send arbitrary requests over the same connection directly to the backend, authenticated with the Kubernetes API server's TLS credentials used to establish the backend connection.
Other sources
With a specially crafted request, users are able to establish a connection through the Kubernetes API server to backend servers, then send arbitrary requests over the same connection directly to the backend, authenticated with the Kubernetes API server’s TLS credentials used to establish the backend connection.
— Red Hat
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2018-1002105?
CVE-2018-1002105 has a high severity level due to its potential to allow unauthorized access to backend servers.
How do I fix CVE-2018-1002105?
To fix CVE-2018-1002105, upgrade Kubernetes to versions 1.10.11, 1.11.5, 1.12.3, or higher.
Which Kubernetes versions are affected by CVE-2018-1002105?
Kubernetes versions prior to 1.10.11, 1.11.5, and 1.12.3 are affected by CVE-2018-1002105.
What kind of vulnerability is CVE-2018-1002105?
CVE-2018-1002105 is a vulnerability related to incorrect handling of error responses in the kube-apiserver.
Can CVE-2018-1002105 lead to data breaches?
Yes, CVE-2018-1002105 can potentially lead to data breaches by allowing arbitrary requests to backend servers.