An incorrect sysctls validation vulnerability was found in CRI-O 1.18 and earlier. The sysctls from the list of "safe" sysctls specified for the cluster will be applied to the host if an attacker is able to create a pod with a hostIPC and hostNetwork kernel namespace.
                
            References
                    | Link | Resource | 
|---|---|
| https://bugzilla.redhat.com/show_bug.cgi?id=2051730 | Issue Tracking Patch Third Party Advisory | 
| https://kubernetes.io/docs/tasks/administer-cluster/sysctl-cluster/#enabling-unsafe-sysctls | Vendor Advisory | 
| https://bugzilla.redhat.com/show_bug.cgi?id=2051730 | Issue Tracking Patch Third Party Advisory | 
| https://kubernetes.io/docs/tasks/administer-cluster/sysctl-cluster/#enabling-unsafe-sysctls | Vendor Advisory | 
Configurations
                    History
                    21 Nov 2024, 06:38
| Type | Values Removed | Values Added | 
|---|---|---|
| References | () https://bugzilla.redhat.com/show_bug.cgi?id=2051730 - Issue Tracking, Patch, Third Party Advisory | |
| References | () https://kubernetes.io/docs/tasks/administer-cluster/sysctl-cluster/#enabling-unsafe-sysctls - Vendor Advisory | 
Information
                Published : 2022-02-09 23:15
Updated : 2024-11-21 06:38
NVD link : CVE-2022-0532
Mitre link : CVE-2022-0532
CVE.ORG link : CVE-2022-0532
JSON object : View
Products Affected
                redhat
- openshift_container_platform
kubernetes
- cri-o
CWE
                
                    
                        
                        CWE-732
                        
            Incorrect Permission Assignment for Critical Resource
