First published: Thu Nov 08 2018(Updated: )
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.
Credit: jordan@liggitt.net
Affected Software | Affected Version | How to fix |
---|---|---|
Kubernetes Kubernetes | >=1.0.0<=1.9.11 | |
Kubernetes Kubernetes | >=1.10.0<=1.10.10 | |
Kubernetes Kubernetes | >=1.11.0<=1.11.4 | |
Kubernetes Kubernetes | >=1.12.0<=1.12.2 | |
Kubernetes Kubernetes | =1.9.12-beta0 | |
Redhat Openshift Container Platform | =3.2 | |
Redhat Openshift Container Platform | =3.3 | |
Redhat Openshift Container Platform | =3.4 | |
Redhat Openshift Container Platform | =3.5 | |
Redhat Openshift Container Platform | =3.6 | |
Redhat Openshift Container Platform | =3.8 | |
Redhat Openshift Container Platform | =3.10 | |
Redhat Openshift Container Platform | =3.11 | |
Netapp Trident |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.