vulntracker.iovulntracker.io
© 2026 vulntracker.io

CVE-2022-23648

Insecure handling of image volumes in containerd CRI plugin

HIGH
7.5
CVSS Score
Published: March 3, 2022 at 12:00 AM UTC
Updated: June 17, 2026 at 04:30 AM UTC
4 products affected across 4 vendorsDebian LinuxFedoraContainerd

Using containerd by containerd?

Get instant alerts when new vulnerabilities affect containerd - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Start FreeSign In
Severity
HIGH7.5
Exploit prediction
EPSS 27%

Description

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Debian Linux· Debiandrupal
95%
11.0
Fedora· Fedora Projectrpm
95%
343536
Containerd· Linuxfoundation
95%
v < 1.4.131.5.0 ≤ v < 1.5.101.6.0 ≤ v < 1.6.1
Affected range stops below 1.4.13, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.5.10, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.6.1, so it looks safe — our inference, not a vendor statement
Containerd· Containerd
60%
v < 1.4.13v < 1.5.10v < 1.6.1
Affected range stops below 1.4.13, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.5.10, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.6.1, so it looks safe — our inference, not a vendor statement

References (11)

ExploitThird Party AdvisoryVDB Entry
Source: [email protected]
http://packetstormsecurity.com/files/166421/containerd-Image-Volume-Insecure-Handling.html
PatchThird Party Advisory
Source: [email protected]
https://github.com/containerd/containerd/commit/10f428dac7cec44c864e1b830a4623af27a9fc70
PatchRelease NotesThird Party Advisory
Source: [email protected]
https://github.com/containerd/containerd/releases/tag/v1.4.13
PatchRelease NotesThird Party Advisory
Source: [email protected]
https://github.com/containerd/containerd/releases/tag/v1.5.10
PatchRelease NotesThird Party Advisory
Source: [email protected]
https://github.com/containerd/containerd/releases/tag/v1.6.1
Third Party Advisory
Source: [email protected]
https://github.com/containerd/containerd/security/advisories/GHSA-crp2-qrr5-8pq7
Vendor Advisory
Source: [email protected]
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/AUDQUQBZJGBWJPMRVB6QCCCRF7O3O4PA/
Vendor Advisory
Source: [email protected]
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HFTS2EF3S7HNYSNZSEJZIJHPRU7OPUV3/

CVSS

7.5HIGHGitHub_M
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-200NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create accountSign in
Free plan, no card