QID 355261

A bug was found in containerd where containers launched through containerd's cri implementation with a specially-crafted image configuration could gain access to read-only copies of arbitrary files and directories on the host.
This may bypass any policy-based enforcement on container setup (including a kubernetes pod security policy) and expose potentially sensitive information.
Kubernetes and crictl can both be configured to use containerd's cri implementation. (
( CVE-2022-23648) a flaw was found in moby (docker engine), where containers were started incorrectly with non-empty inheritable linux process capabilities.
This flaw allows an attacker with access to programs with inheritable file capabilities to elevate those capabilities to the permitted set when execve(2) runs.
Containers using linux users and groups to perform privilege separation inside the container are most directly impacted. (
( CVE-2022-24769) a bug was found in containerd's cri implementation where programs inside a container can cause the containerd daemon to consume memory without bound during invocation of the execsync api.
This can cause containerd to consume all available memory on the computer, denying service to other legitimate workloads.
Kubernetes and crictl can both be configured to use containerd's cri implementation; execsync may be used when running probes or when executing processes via an exec facility. (
( CVE-2022-31030) a flaw was found in moby.
This flaw allows an attacker to bypass primary group restrictions due to a flaw in the supplementary group access setup.

Successful exploitation of this vulnerability could lead to a securitybreach or could affect integrity, availability, and confidentiality.