Kubernetes API Server denial of service vulnerability from malicious YAML payloads
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Kubernetes | Kubernetes | affected |
|
Configuration 1 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat OpenShift Container Platform 3.11 | |||
| atomic-openshift-0:3.11.232-1.git.0.a5bc32f.el7 | cpe:/a:redhat:openshift:3.11::el7 | RHSA-2020:2479 | 2020-06-18T00:00:00Z |
| Red Hat OpenShift Container Platform 4.3 | |||
| openshift4/ose-openshift-apiserver-rhel7:v4.3.9-202003230345 | cpe:/a:redhat:openshift:4.3::el7 | RHSA-2020:0933 | 2020-04-01T00:00:00Z |
| Red Hat OpenShift Container Platform 4.5 | |||
| openshift4/ose-hyperkube:v4.5.0-202007100518.p0 | cpe:/a:redhat:openshift:4.5::el7 | RHSA-2020:2412 | 2020-07-13T00:00:00Z |
| openshift4/ose-oauth-server-rhel7:v4.5.0-202007012112.p0 | cpe:/a:redhat:openshift:4.5::el7 | RHSA-2020:2412 | 2020-07-13T00:00:00Z |
| openshift-0:4.5.0-202007012112.p0.git.0.582d7fc.el7 | cpe:/a:redhat:openshift:4.5::el7 | RHSA-2020:2413 | 2020-07-13T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2021-2608 | The Kubernetes API Server component in versions 1.1-1.14, and versions prior to 1.15.10, 1.16.7 and 1.17.3 allows an authorized user who sends malicious YAML payloads to cause the kube-apiserver to consume excessive CPU cycles while parsing YAML. |
Github GHSA |
GHSA-wxc4-f4m6-wwqv | Excessive Platform Resource Consumption within a Loop in Kubernetes |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 3.2% (3.157% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.