Resource exhaustion in Kubernetes Cri-O

CVE-2022-1708

A vulnerability was found in CRI-O that causes memory or disk space exhaustion on the node for anyone with access to the Kube API. The ExecSync request runs commands in a container and logs the output of the command. This output is then read by CRI-O after command execution, and it is read in a manner where the entire file corresponding to the output of the command is read in. Thus, if the output of the command is large it is possible to exhaust the memory or the disk space of the node when CRI-O reads the output of the command. The highest threat from this vulnerability is system availability.

Vulnerability class: DoS (Denial of Service)

EPSS: 0.031 (87.1th percentile) — read the EPSS interpretation.

CVSS v3 metric

CVSS v3 base score 7.5 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

Affected products

Weakness classification (CWE)

Public proof-of-concept exploits

References

Frequently asked questions

What is CVE-2022-1708?
CVE-2022-1708 is a high-severity vulnerability in Kubernetes Cri-O, classified under Uncontrolled Resource Consumption. CVSS score: 7.5/10. Published 2022-06-07.
How severe is CVE-2022-1708?
High severity. CVSS v3 base score is 7.5 out of 10.
Is CVE-2022-1708 known to be exploited?
2 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.