Skip to content

XML Entity Expansion and Improper Input Validation in Kubernetes API server

High severity GitHub Reviewed Published May 18, 2021 to the GitHub Advisory Database • Updated Sep 29, 2023

Package

gomod k8s.io/kubernetes (Go)

Affected versions

>= 1.0.0, < 1.13.12
>= 1.14.0, < 1.14.8
>= 1.15.0, < 1.15.5
>= 1.16.0, < 1.16.2

Patched versions

1.13.12
1.14.8
1.15.5
1.16.2

Description

Improper input validation in the Kubernetes API server in versions v1.0-1.12 and versions prior to v1.13.12, v1.14.8, v1.15.5, and v1.16.2 allows authorized users to send malicious YAML or JSON payloads, causing the API server to consume excessive CPU or memory, potentially crashing and becoming unavailable. Prior to v1.14.0, default RBAC policy authorized anonymous users to submit requests that could trigger this vulnerability. Clusters upgraded from a version prior to v1.14.0 keep the more permissive policy by default for backwards compatibility.

Specific Go Packages Affected

k8s.io/kubernetes/pkg/apiserver

References

Reviewed May 17, 2021
Published to the GitHub Advisory Database May 18, 2021
Last updated Sep 29, 2023

Severity

High

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
None
Integrity
None
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.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

2.588%
(91st percentile)

Weaknesses

CVE ID

CVE-2019-11253

GHSA ID

GHSA-pmqp-h87c-mr78

Source code

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