CVE-2018-1002105
high-risk
Published 2018-12-05
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.
Do I need to act?
!
90.7% chance of exploitation in next 30 days
EPSS score — higher than 9% of all CVEs
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
9
CVSS 9.8/10
Critical
NETWORK
/ LOW complexity
Affected Products (11)
Affected Vendors
References (40)
Third Party Advisory
http://www.securityfocus.com/bid/106068
Third Party Advisory
https://access.redhat.com/errata/RHSA-2018:3537
Third Party Advisory
https://access.redhat.com/errata/RHSA-2018:3549
Third Party Advisory
https://access.redhat.com/errata/RHSA-2018:3551
Third Party Advisory
https://access.redhat.com/errata/RHSA-2018:3598
Third Party Advisory
https://access.redhat.com/errata/RHSA-2018:3624
Third Party Advisory
https://access.redhat.com/errata/RHSA-2018:3742
Third Party Advisory
https://access.redhat.com/errata/RHSA-2018:3752
Third Party Advisory
https://access.redhat.com/errata/RHSA-2018:3754
Issue Tracking
https://github.com/kubernetes/kubernetes/issues/71411
Third Party Advisory
https://security.netapp.com/advisory/ntap-20190416-0001/
and 20 more references
68
/ 100
high-risk
Severity
32/34 · Critical
Exploitability
20/34 · Moderate
Exposure
16/34 · Moderate