4.8 MEDIUM
- CVSS version: 3.1
- Attack vector (AV): LOCAL
- Attack complexity (AC): LOW
- Privileges required (PR): LOW
- User interaction (UI): REQUIRED
- Scope (S): UNCHANGED
- Confidentiality impact (C): LOW
- Integrity impact (I): LOW
- Availability impact (A): LOW
Cri-o: security regression of cve-2022-27652
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.
References
- RHSA-2022:7398 x_refsource_REDHAT vendor-advisory
- https://access.redhat.com/security/cve/CVE-2022-3466 x_refsource_REDHAT vdb-entry
- RHBZ#2134063 issue-tracking x_refsource_REDHAT
- RHSA-2022:7398 x_refsource_REDHAT vendor-advisory
- https://access.redhat.com/security/cve/CVE-2022-3466 x_refsource_REDHAT vdb-entry
- RHBZ#2134063 issue-tracking x_refsource_REDHAT
- RHSA-2022:7398 x_refsource_REDHAT vendor-advisory
- https://access.redhat.com/security/cve/CVE-2022-3466 x_refsource_REDHAT vdb-entry
- RHBZ#2134063 issue-tracking x_refsource_REDHAT
- RHSA-2022:7398 x_refsource_REDHAT vendor-advisory x_transferred
- https://access.redhat.com/security/cve/CVE-2022-3466 x_refsource_REDHAT vdb-entry x_transferred
- RHBZ#2134063 issue-tracking x_refsource_REDHAT x_transferred
Affected products
- *
Matching in nixpkgs
pkgs.cri-o
Open Container Initiative-based implementation of the Kubernetes Container Runtime Interface
-
nixos-unstable -
- nixpkgs-unstable 1.34.0
pkgs.cri-o-unwrapped
Open Container Initiative-based implementation of the Kubernetes Container Runtime Interface
-
nixos-unstable -
- nixpkgs-unstable 1.34.0
Package maintainers
-
@saschagrunert Sascha Grunert <mail@saschagrunert.de>
-
@vdemeester Vincent Demeester <vincent@sbr.pm>