Vulnerabilities · 2018 · Kubernetes
CVE-2018-1002105
Kubernetes 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.
High priority: this vulnerability is rated critical and can be attacked over the network without a login.
Affected products
Kubernetes, Openshift Container Platform, Trident. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Kubernetes runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/kubernetes/kubernetes/issues/71411 · Mitigation
- www.coalfire.com/The-Coalfire-Blog/December-2018/Kubernetes-Vulnerability-What-You-Can-Sho · Mitigation
- www.securityfocus.com/bid/106068 · Third Party Advisory
- access.redhat.com/errata/RHSA-2018:3537 · Third Party Advisory
- access.redhat.com/errata/RHSA-2018:3549 · Third Party Advisory
- access.redhat.com/errata/RHSA-2018:3551 · Third Party Advisory
- access.redhat.com/errata/RHSA-2018:3598 · Third Party Advisory
- access.redhat.com/errata/RHSA-2018:3624 · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2018-1002105
- cve.org/CVERecord?id=CVE-2018-1002105
More vulnerabilities in Kubernetes products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.