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.
References
Link | Resource |
---|---|
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 |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: redhat
Published: 2022-03-16T14:03:40
Updated: 2022-03-16T14:03:39
Reserved: 2022-03-01T00:00:00
Link: CVE-2022-0811
JSON object: View
NVD Information
Status : Analyzed
Published: 2022-03-16T15:15:16.123
Modified: 2022-03-28T13:18:27.817
Link: CVE-2022-0811
JSON object: View
Redhat Information
No data.
CWE