CVE-2022-0532

Description

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.

Category

4.2
CVSS
Severity: Medium
CVSS 3.1 •
CVSS 2.0 •
EPSS 0.07%
Vendor Advisory kubernetes.io
Affected: n/a cri-o
Published at:
Updated at:

References

Link Tags
https://bugzilla.redhat.com/show_bug.cgi?id=2051730 issue tracking third party advisory patch
https://kubernetes.io/docs/tasks/administer-cluster/sysctl-cluster/#enabling-unsafe-sysctls vendor advisory

Frequently Asked Questions

What is the severity of CVE-2022-0532?
CVE-2022-0532 has been scored as a medium severity vulnerability.
How to fix CVE-2022-0532?
To fix CVE-2022-0532, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2022-0532 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2022-0532 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2022-0532?
CVE-2022-0532 affects n/a cri-o.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.