CVE-2018-1002105
Description
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.
How to fix
- github.com/kubernetes/kubernetes1.10.11, 1.11.5, 1.12.3 or later
- access.redhat.com/errata/RHSA-2018:3549
- access.redhat.com/errata/RHSA-2018:3752
- access.redhat.com/errata/RHSA-2018:3624
- access.redhat.com/errata/RHSA-2018:3742
- access.redhat.com/errata/RHSA-2018:3754
- access.redhat.com/errata/RHSA-2018:3537
- access.redhat.com/errata/RHSA-2018:3598
- access.redhat.com/errata/RHSA-2018:3551
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| kubernetes kubernetes | 1.0.0 ≤ v ≤ 1.9.11, 1.10.0 ≤ v ≤ 1.10.10, 1.11.0 ≤ v ≤ 1.11.4, 1.12.0 ≤ v ≤ 1.12.2, 1.9.12 | — |
| redhat openshift_container_platform | 3.2, 3.3, 3.4, 3.5, 3.6, 3.8, 3.10, 3.11 | — |
| netapp trident | No range specified | — |
| github.com/kubernetes/kubernetesGo | v < 1.10.11, 1.11.0 ≤ v < 1.11.5, 1.12.0 ≤ v < 1.12.3 | 1.10.11, 1.11.5, 1.12.3 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.