CVE-2022-23648
Published: 2 March 2022
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.
From the Ubuntu Security Team
It was discovered that containerd allows attackers to gain access to read-only copies of arbitrary files and directories on the host via a specially-crafted image configuration. An attacker could possibly use this issue to obtain sensitive information.
Notes
| Author | Note |
|---|---|
| mdeslaur | While this was fixed in USN-5311-1, a subsequent SRU regressed the security update. |
Priority
Status
| Package | Release | Status |
|---|---|---|
|
containerd Launchpad, Ubuntu, Debian |
bionic |
Released
(1.5.5-0ubuntu3~18.04.2)
|
| focal |
Released
(1.5.9-0ubuntu1~20.04.4)
|
|
| impish |
Released
(1.5.9-0ubuntu1~21.10.3)
|
|
| jammy |
Released
(1.5.9-0ubuntu2)
|
|
| upstream |
Released
(1.6.1,1.5.11,1.4.13)
|
|
| xenial |
Released
(1.2.6-0ubuntu1~16.04.6+esm1)
|
Severity score breakdown
| Parameter | Value |
|---|---|
| Base score | 7.5 |
| Attack vector | Network |
| Attack complexity | Low |
| Privileges required | None |
| User interaction | None |
| Scope | Unchanged |
| Confidentiality | High |
| Integrity impact | None |
| Availability impact | None |
| Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |