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 | 
| 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 | 
Configurations
                    Configuration 1 (hide)
| 
 | 
History
                    21 Nov 2024, 06:39
| Type | Values Removed | Values Added | 
|---|---|---|
| References | () https://bugzilla.redhat.com/show_bug.cgi?id=2059475 - Issue Tracking, Third Party Advisory | |
| References | () https://github.com/cri-o/cri-o/security/advisories/GHSA-6x2m-w449-qwx7 - Third Party Advisory | 
Information
                Published : 2022-03-16 15:15
Updated : 2024-11-21 06:39
NVD link : CVE-2022-0811
Mitre link : CVE-2022-0811
CVE.ORG link : CVE-2022-0811
JSON object : View
Products Affected
                kubernetes
- cri-o
CWE
                
                    
                        
                        CWE-94
                        
            Improper Control of Generation of Code ('Code Injection')
