Bug 2051730 (CVE-2022-0532)
Summary: | CVE-2022-0532 cri-o: pod with access to 'hostIPC' and 'hostNetwork' kernel namespace allows sysctl from the list of safe sysctls to be applied to the host | ||
---|---|---|---|
Product: | [Other] Security Response | Reporter: | Przemyslaw Roguski <proguski> |
Component: | vulnerability | Assignee: | Red Hat Product Security <security-response-team> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | unspecified | CC: | aos-bugs, blaise, bmontgom, bradley.g.smith, ebakerupw, eparis, jakubr, jburrell, jokerman, nstielau, pehunt, rphillips, ryncsn, santiago, sponnaga, vkumar |
Target Milestone: | --- | Keywords: | Security |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | cri-o 1.23.1 | Doc Type: | If docs needed, set a value |
Doc Text: |
An incorrect sysctls validation vulnerability was found in CRI-O. The sysctls from the list of "safe" sysctls specified for the cluster [0] will be applied to the host if an attacker can create a pod with a `hostIPC` and `hostNetwork` kernel namespace.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2022-03-10 19:45:43 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 2051905, 2051906 | ||
Bug Blocks: | 2050386 |
Description
Przemyslaw Roguski
2022-02-07 22:06:03 UTC
Created cri-o tracking bugs for this issue: Affects: fedora-all [bug 2051906] All currently supported version of CRI-O are affected by this vulnerability. Upstream fix: https://github.com/cri-o/cri-o/pull/5610 This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.10 Via RHSA-2022:0055 https://access.redhat.com/errata/RHSA-2022:0055 This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2022-0532 This comment was flagged a spam, view the edit history to see the original text if required. |