Vulnerabilities · 2022 · Kubernetes
CVE-2022-3466
Kubernetes Cri-o vulnerability
The version of cri-o as released for Red Hat OpenShift Container Platform 4.9.48, 4.10.31, and 4.11.6 via RHBA-2022:6316, RHBA-2022:6257, and RHBA-2022:6658, respectively, included an incorrect version of cri-o missing the fix for CVE-2022-27652, which was previously fixed in OCP 4.9.41 and 4.10.12 via RHBA-2022:5433 and RHSA-2022:1600. This issue could allow an attacker with access to programs with inheritable file capabilities to elevate those capabilities to the permitted set when execve(2) runs. For more details, see https://access.redhat.com/security/cve/CVE-2022-27652.
Affected products
Cri-o, Openshift Container Platform. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Kubernetes Cri-o runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- access.redhat.com/errata/RHSA-2022:7398 · Vendor Advisory
- access.redhat.com/security/cve/CVE-2022-3466 · Vendor Advisory
- bugzilla.redhat.com/show_bug.cgi?id=2134063 · Vendor Advisory
- nvd.nist.gov/vuln/detail/CVE-2022-3466
- cve.org/CVERecord?id=CVE-2022-3466
More vulnerabilities in Kubernetes products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.