CVE-2022-23648: Insecure handling of image volumes in containerd CRI plugin
First published: Wed Mar 02 2022(Updated: )
### 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](https://github.com/containerd/project/blob/main/SECURITY.md). ### For more information If you have any questions or comments about this advisory: * Open an issue in [containerd](https://github.com/containerd/containerd/issues/new/choose) * Email us at [security@containerd.io](mailto:security@containerd.io)
Credit: security-advisories@github.com security-advisories@github.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linuxfoundation Containerd | <1.4.13 | |
| Linuxfoundation Containerd | >=1.5.0<1.5.10 | |
| Linuxfoundation Containerd | >=1.6.0<1.6.1 | |
| Debian Debian Linux | =11.0 | |
| Fedoraproject Fedora | =34 | |
| Fedoraproject Fedora | =35 | |
| Fedoraproject Fedora | =36 | |
| debian/containerd | 1.4.13~ds1-1~deb11u4 1.4.13~ds1-1~deb11u2 1.6.20~ds1-1 1.6.20~ds1-2 | |
| go/github.com/containerd/containerd | >=1.6.0<1.6.1 | 1.6.1 |
| go/github.com/containerd/containerd | >=1.5.0<1.5.10 | 1.5.10 |
| go/github.com/containerd/containerd | <1.4.13 | 1.4.13 |
| <1.4.13 | ||
| >=1.5.0<1.5.10 | ||
| >=1.6.0<1.6.1 | ||
| =11.0 | ||
| =34 | ||
| =35 | ||
| =36 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- http://packetstormsecurity.com/files/166421/containerd-Image-Volume-Insecure-Handling.html
- https://github.com/containerd/containerd/commit/10f428dac7cec44c864e1b830a4623af27a9fc70
- https://github.com/containerd/containerd/releases/tag/v1.4.13
- https://github.com/containerd/containerd/releases/tag/v1.5.10
- https://github.com/containerd/containerd/releases/tag/v1.6.1
- https://github.com/containerd/containerd/security/advisories/GHSA-crp2-qrr5-8pq7
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/AUDQUQBZJGBWJPMRVB6QCCCRF7O3O4PA/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HFTS2EF3S7HNYSNZSEJZIJHPRU7OPUV3/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OCCARJ6FU4MWBTXHZNMS7NELPDBIX2VO/
- https://www.debian.org/security/2022/dsa-5091
- https://www.openwall.com/lists/oss-security/2022/03/02/1
- https://security-tracker.debian.org/tracker/CVE-2022-23648
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/OCCARJ6FU4MWBTXHZNMS7NELPDBIX2VO/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/AUDQUQBZJGBWJPMRVB6QCCCRF7O3O4PA/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HFTS2EF3S7HNYSNZSEJZIJHPRU7OPUV3/
- https://security.gentoo.org/glsa/202401-31
- https://nvd.nist.gov/vuln/detail/CVE-2022-23648
- https://github.com/advisories/GHSA-crp2-qrr5-8pq7 (Advisory)
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.
- collector/nvd-index
- collector/security-tracker-debian
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/remedy
- agent/title
- agent/weakness
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/author
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-crp2-qrr5-8pq7
- alias/CVE-2022-23648
- agent/last-modified-date
- agent/references
- agent/description
- agent/first-publish-date
- agent/softwarecombine
- agent/event
- agent/tags
- collector/nvd-cve
- collector/github-advisory
- vendor/linuxfoundation
- canonical/linuxfoundation containerd
- version/linuxfoundation containerd/1.5.0
- version/linuxfoundation containerd/1.6.0
- vendor/debian
- canonical/debian debian linux
- version/debian debian linux/11.0
- vendor/fedoraproject
- canonical/fedoraproject fedora
- version/fedoraproject fedora/34
- version/fedoraproject fedora/35
- version/fedoraproject fedora/36
- package-manager/debian
- package-manager/go