Insecure handling of image volumes in containerd CRI plugin
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| containerd | containerd | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DSA |
DSA-5091-1 | containerd security update |
EUVD |
EUVD-2022-1411 | 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. |
Github GHSA |
GHSA-crp2-qrr5-8pq7 | containerd CRI plugin: Insecure handling of image volumes |
Ubuntu USN |
USN-5311-1 | containerd vulnerability |
Ubuntu USN |
USN-5311-2 | containerd regression |
Ubuntu USN |
USN-5521-1 | containerd vulnerabilities |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 27.4% (27.392% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.