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, 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.
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Dec 5, 2018, 9:00:00 PM
dateUpdated: Aug 5, 2024, 12:47:57 PM
12 related source bulletins · separate from aliases
openSUSE-SU-2020:0554-1: Security update for kubernetes
RHSA-2018:3598: Red Hat Security Advisory: OpenShift Container Platform 3.6 security update
CVE-2018-1002105
RHSA-2018:3551: Red Hat Security Advisory: OpenShift Container Platform 3.8 security update
CVE-2018-1002105
RHSA-2018:3624: Red Hat Security Advisory: OpenShift Container Platform 3.5 security update
CVE-2018-1002105
RHSA-2018:3752: Red Hat Security Advisory: OpenShift Container Platform 3.4 security update
CVE-2018-1002105
RHSA-2018:3537: Red Hat Security Advisory: OpenShift Container Platform 3.11 security update
CVE-2018-3830 · CVE-2018-12115 · CVE-2018-1002105
RHSA-2018:3549: Red Hat Security Advisory: OpenShift Container Platform 3.10 security update
CVE-2018-1002105
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
The original JSON retains the logical configuration operators, exclusions and version bounds.
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.