CVE-2022-23648 containerd is a container runtime available as a daemon for Linux and Windows

CVE-2022-23648 containerd is a container runtime available as a daemon for Linux and Windows

Additionally, containerd versions prior to 1.5.10 have been found to be vulnerable to a denial of service due to a NULL-pointer dereference when a small number of simultaneous connections are received. This can be mitigated by lowering the rate at which connections are processed. A mitigations for containerd users has been released and can be found here.

Container Runtime Interface A bug was discovered in the CRI implementation of containerd prior to versions 1.6.1, 1.5.10, and 1.4.12 where a malicious container could gain access to read-only copies of arbitrary files and directories on the host operating system. 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. This bug has been fixed in containerd 1.6.1, 1.5.10, and 1.4.12. Users should update to these versions to resolve the issue. Additionally, containerd versions prior to 1.5.10 have been found to be vulnerable to a denial of service due to a NULL-pointer dereference when a small number of simultaneous connections are received. This can be mitigated by lowering the rate at which connections are processed. A mitigations for containerd users has been released and can be found here.

Container Runtime Interface (CRI)

In this article, the authors talk about an issue with the Container Runtime Interface (CRI) implementation of containerd. In short, a bug was discovered in the CRI implementation of containerd prior to versions 1.6.1, 1.5.10, and 1.4.12 where a malicious container could gain access to read-only copies of arbitrary files and directories on the host operating system. This bug has been fixed in containerd 1.6.1, 1.5.10, and 1.4.12 and users should update to these versions to resolve the issue or risk having their data exposed by malicious containers running on their Kubernetes clusters or crictl configurations that use pre-v1.6 version of containerd

References

Subscribe to CVE.news
Don’t miss out on the latest issues. Sign up now to get access to the library of members-only issues.
jamie@example.com
Subscribe