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…
4 public exploits exists; no exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 87%. Fixed in v1.10.11, v1.11.5 and v1.12.3.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Kubernetes | <v1.10.11, <v1.11.5, <v1.12.3, =v1.0.x, =v1.1.x, =v1.2.x, =v1.3.x, =v1.4.x, =v1.5.x, =v1.6.x, =v1.7.x, =v1.8.x, =v1.9.x | v1.10.11, v1.11.5, v1.12.3 |
Exploit evidence
4 public sources
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket