Vulnerability 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.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Kubernetes | Cri-O | >= 1.19.0, < 1.19.6 |
Related Weaknesses (CWE)
References
- https://bugzilla.redhat.com/show_bug.cgi?id=2059475Issue TrackingThird Party Advisory
- https://github.com/cri-o/cri-o/security/advisories/GHSA-6x2m-w449-qwx7Third Party Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=2059475Issue TrackingThird Party Advisory
- https://github.com/cri-o/cri-o/security/advisories/GHSA-6x2m-w449-qwx7Third Party Advisory
FAQ
What is CVE-2022-0811?
CVE-2022-0811 is a vulnerability with a CVSS score of 8.8 (HIGH). 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 es...
How severe is CVE-2022-0811?
CVE-2022-0811 has been rated HIGH with a CVSS base score of 8.8/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2022-0811?
Check the references section above for vendor advisories and patch information. Affected products include: Kubernetes Cri-O.