Strix
26.1K

CVE-2022-1708

HIGHCVSS 7.5/10EPSS 2.80%

Last modified

CVE-2022-1708 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. 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. EPSS estimates a 2.80% chance of exploitation in the next 30 days.

Description

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.

Metrics

CVSS 3.1
7.5/10

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS Probability
2.80%

84.7th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
KubernetesCri-O< 1.19.7
KubernetesCri-O>= 1.20.0, < 1.20.8
KubernetesCri-O>= 1.21.0, < 1.21.8
KubernetesCri-O>= 1.22.0, < 1.22.5
KubernetesCri-O>= 1.23.0, < 1.23.3
KubernetesCri-O1.24.0
FedoraprojectFedora36
RedhatOpenshift Container Platform3.11
RedhatOpenshift Container Platform4.0
RedhatOpenshift Container Platform4.9
RedhatOpenshift Container Platform4.10
RedhatEnterprise Linux7.0
RedhatEnterprise Linux8.0
RedhatEnterprise Linux9.0

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is 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.
How severe is CVE-2022-1708?
CVE-2022-1708 has a CVSS score of 7.5/10 (HIGH severity). The EPSS model estimates a 2.80% probability of exploitation in the next 30 days.
How do I fix CVE-2022-1708?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2022-1708?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST