First published: Thu Aug 25 2022(Updated: )
Incorrect handling of the supplementary groups in the CRI-O container engine might lead to sensitive information disclosure or possible data modification if an attacker has direct access to the affected container where supplementary groups are used to set access permissions and is able to execute a binary code in that container.
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/cri-o | <1.25.0 | 1.25.0 |
redhat/cri-o | <0:1.23.5-11.rhaos4.10.gitfc32aac.el7 | 0:1.23.5-11.rhaos4.10.gitfc32aac.el7 |
redhat/cri-o | <0:1.24.5-5.rhaos4.11.git8bf967b.el8 | 0:1.24.5-5.rhaos4.11.git8bf967b.el8 |
redhat/cri-o | <0:1.25.1-5.rhaos4.12.git6005903.el8 | 0:1.25.1-5.rhaos4.12.git6005903.el8 |
go/github.com/cri-o/cri-o | <1.25.0 | 1.25.0 |
Kubernetes CRI-O | =1.25.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Appears in the following advisories)
CVE-2022-2995 is a vulnerability in the CRI-O container engine that can lead to sensitive information disclosure or possible data modification.
The severity of CVE-2022-2995 is high with a CVSS score of 7.1.
CVE-2022-2995 affects CRI-O by incorrectly handling the supplementary groups, which can result in sensitive information disclosure or possible data modification.
To mitigate CVE-2022-2995, update CRI-O to version 1.25.0 or apply the recommended patches provided by Red Hat.
You can find more information about CVE-2022-2995 on the NIST NVD website, the GitHub pull request, and the Bentham's Gaze article.