Skip to content

Privilege Escalation in Kubernetes

Critical severity GitHub Reviewed Published Feb 15, 2022 to the GitHub Advisory Database • Updated Jan 9, 2023

Package

gomod github.com/kubernetes/kubernetes (Go)

Affected versions

< 1.10.11
>= 1.11.0, < 1.11.5
>= 1.12.0, < 1.12.3

Patched versions

1.10.11
1.11.5
1.12.3

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.

References

Reviewed May 20, 2021
Published to the GitHub Advisory Database Feb 15, 2022
Last updated Jan 9, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

37.549%
(97th percentile)

Weaknesses

CVE ID

CVE-2018-1002105

GHSA ID

GHSA-579h-mv94-g4gp

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.