CVE-2022-0532
First published: Thu Jan 27 2022(Updated: )
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.
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| redhat/cri-o | <0:1.23.0-92.rhaos4.10.gitdaab4d1.el7 | 0:1.23.0-92.rhaos4.10.gitdaab4d1.el7 |
| redhat/cri-o | <0:1.19.5-3.rhaos4.6.git91f8458.el8 | 0:1.19.5-3.rhaos4.6.git91f8458.el8 |
| redhat/cri-o | <0:1.20.6-11.rhaos4.7.git76ea3d0.el8 | 0:1.20.6-11.rhaos4.7.git76ea3d0.el8 |
| redhat/cri-o | <0:1.21.5-2.rhaos4.8.gitaf64931.el8 | 0:1.21.5-2.rhaos4.8.gitaf64931.el8 |
| redhat/cri-o | <0:1.22.2-2.rhaos4.9.gitb030be8.el7 | 0:1.22.2-2.rhaos4.9.gitb030be8.el7 |
| Kubernetes CRI-O | <=1.18 | |
| Redhat Openshift Container Platform | =4.0 | |
| redhat/cri-o | <1.23.1 | 1.23.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://bugzilla.redhat.com/show_bug.cgi?id=2051730
- https://kubernetes.io/docs/tasks/administer-cluster/sysctl-cluster/#enabling-unsafe-sysctls
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2051906
- https://github.com/cri-o/cri-o/pull/5610
- https://access.redhat.com/errata/RHSA-2022:0055
- https://access.redhat.com/security/cve/cve-2022-0532
- https://www.cve.org/CVERecord?id=CVE-2022-0532 https://nvd.nist.gov/vuln/detail/CVE-2022-0532 https://github.com/cri-o/cri-o/security/advisories/GHSA-w2j5-3rcx-vx7x https://kubernetes.io/docs/tasks/administer-cluster/sysctl-cluster/#enabling-unsafe-sysctls
- https://access.redhat.com/errata/RHSA-2022:0866
- https://access.redhat.com/errata/RHSA-2022:0870
- https://access.redhat.com/errata/RHBA-2022:0793
- https://access.redhat.com/errata/RHBA-2022:0794
Parent vulnerabilities
(Appears in the following advisories)
Frequently Asked Questions
What is CVE-2022-0532?
CVE-2022-0532 is an incorrect sysctls validation vulnerability found in CRI-O.
How does CVE-2022-0532 impact CRI-O?
CVE-2022-0532 allows an attacker to apply sysctls from the list of "safe" sysctls to the host if they can create a pod with a hostIPC and hostNetwork kernel namespace.
What is the severity level of CVE-2022-0532?
CVE-2022-0532 has a severity level of medium.
Which versions of CRI-O are affected by CVE-2022-0532?
CRI-O versions 1.18 and earlier are affected by CVE-2022-0532.
How can I fix CVE-2022-0532 in CRI-O?
To fix CVE-2022-0532, upgrade to CRI-O version 1.23.1 or later.
- agent/author
- agent/description
- agent/event
- agent/first-publish-date
- agent/last-modified-date
- agent/references
- agent/remedy
- agent/severity
- agent/softwarecombine
- agent/tags
- agent/type
- agent/weakness
- collector/nvd-index
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2022-0532
- agent/software-canonical-lookup
- collector/redhat-cve
- vendor/kubernetes
- canonical/kubernetes cri-o
- version/kubernetes cri-o/1.18
- vendor/redhat
- canonical/redhat openshift container platform
- version/redhat openshift container platform/4.0
- package-manager/redhat