CVE-2022-0811

Description

A flaw was found in CRI-O in the way it set kernel options for a pod. This issue allows anyone with rights to deploy a pod on a Kubernetes cluster that uses the CRI-O runtime to achieve a container escape and arbitrary code execution as root on the cluster node, where the malicious pod was deployed.

Category

8.8
CVSS
Severity: High
CVSS 3.1 •
CVSS 2.0 •
EPSS 22.41% Top 5%
Third-Party Advisory redhat.com Third-Party Advisory github.com
Affected: n/a CRI-O
Published at:
Updated at:

References

Link Tags
https://bugzilla.redhat.com/show_bug.cgi?id=2059475 issue tracking third party advisory
https://github.com/cri-o/cri-o/security/advisories/GHSA-6x2m-w449-qwx7 third party advisory

Frequently Asked Questions

What is the severity of CVE-2022-0811?
CVE-2022-0811 has been scored as a high severity vulnerability.
How to fix CVE-2022-0811?
To fix CVE-2022-0811, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2022-0811 being actively exploited in the wild?
It is possible that CVE-2022-0811 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~22% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2022-0811?
CVE-2022-0811 affects n/a CRI-O.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.