CVE-2022-23648: Insecure handling of image volumes in containerd CRI plugin
Impact
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.
Patches
This bug has been fixed in containerd 1.6.1, 1.5.10 and 1.4.13. Users should update to these versions to resolve the issue.
Workarounds
Ensure that only trusted images are used.
Credits
The containerd project would like to thank Felix Wilhelm of Google Project Zero for responsibly disclosing this issue in accordance with the containerd security policy.
For more information
If you have any questions or comments about this advisory:
Open an issue in containerd Email us at security@containerd.io
Other sources
containerd is a container runtime available as a daemon for Linux and Windows. A bug was found in containerd prior to versions 1.6.1, 1.5.10, and 1.14.12 where containers launched through containerd’s CRI implementation on Linux 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. 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.
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2022-23648?
The severity of CVE-2022-23648 is high with a CVSS score of 7.5.
Which versions of containerd are affected by CVE-2022-23648?
containerd versions prior to 1.4.13, 1.5.10, and 1.6.1 are affected by CVE-2022-23648.
How can containers launch through containerd's CRI implementation be exploited by CVE-2022-23648?
Containers launched through containerd's CRI implementation on Linux with a specially-crafted image configuration can gain unauthorized read access.
Is containerd affected on Windows by CVE-2022-23648?
No, containerd on Windows is not affected by CVE-2022-23648.
How can I fix CVE-2022-23648 in containerd?
To fix CVE-2022-23648, update containerd to versions 1.6.1, 1.5.10, or 1.4.13, depending on the affected version.