Vulnerabilities · 2022 · Kubernetes
CVE-2022-0811
Kubernetes Cri-o vulnerability
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.
Affected products
Cri-o. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Kubernetes Cri-o runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- bugzilla.redhat.com/show_bug.cgi?id=2059475 · Third Party Advisory
- github.com/cri-o/cri-o/security/advisories/GHSA-6x2m-w449-qwx7 · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2022-0811
- cve.org/CVERecord?id=CVE-2022-0811
More vulnerabilities in Kubernetes products
CVE-2024-5154CVE-2023-5528CVE-2023-5044CVE-2023-5043CVE-2023-3955CVE-2023-3893CVE-2023-3676CVE-2023-2878All 89
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.