Описание
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.
A privilege escalation vulnerability exists in OpenShift Container Platform which allows for compromise of pods running co-located on a compute node. This access could include access to all secrets, pods, environment variables, running pod/container processes, and persistent volumes, including in privileged containers.
Отчет
In versions 3.6 and higher of OpenShift Container Platform, this vulnerability allows cluster-admin level access to any API hosted by an aggregated API server. This includes the ‘service catalog’ API which is installed by default in 3.7 and later. Cluster-admin level access to the service catalog allows creation of brokered services by an unauthenticated user with escalated privileges in any namespace and on any node. This could lead to an attacker being allowed to deploy malicious code, or alter existing services.
Меры по смягчению последствий
See the vulnerability article for mitigation procedures.
Затронутые пакеты
| Платформа | Пакет | Состояние | Рекомендация | Релиз |
|---|---|---|---|---|
| Red Hat OpenShift Enterprise 3.0 | openshift | Will not fix | ||
| Red Hat OpenShift Container Platform 3.10 | atomic-enterprise-service-catalog | Fixed | RHSA-2018:3549 | 20.11.2018 |
| Red Hat OpenShift Container Platform 3.10 | atomic-openshift | Fixed | RHSA-2018:3549 | 20.11.2018 |
| Red Hat OpenShift Container Platform 3.10 | atomic-openshift-descheduler | Fixed | RHSA-2018:3549 | 20.11.2018 |
| Red Hat OpenShift Container Platform 3.10 | atomic-openshift-dockerregistry | Fixed | RHSA-2018:3549 | 20.11.2018 |
| Red Hat OpenShift Container Platform 3.10 | atomic-openshift-node-problem-detector | Fixed | RHSA-2018:3549 | 20.11.2018 |
| Red Hat OpenShift Container Platform 3.10 | atomic-openshift-web-console | Fixed | RHSA-2018:3549 | 20.11.2018 |
| Red Hat OpenShift Container Platform 3.10 | golang-github-prometheus-node_exporter | Fixed | RHSA-2018:3549 | 20.11.2018 |
| Red Hat OpenShift Container Platform 3.10 | openshift-ansible | Fixed | RHSA-2018:3549 | 20.11.2018 |
| Red Hat OpenShift Container Platform 3.10 | openshift-enterprise-cluster-capacity | Fixed | RHSA-2018:3549 | 20.11.2018 |
Показывать по
Дополнительная информация
Статус:
9.8 Critical
CVSS3
Связанные уязвимости
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.
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.
In all Kubernetes versions prior to v1.10.11, v1.11.5, and v1.12.3, in ...
9.8 Critical
CVSS3