Advisory

GHSA-crp2-qrr5-8pq7

Also known as: CVE-2022-23648, GO-2022-0344

Summary

containerd CRI plugin: Insecure handling of image volumes

Details

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:

Severity

High Basis: The source's own band: HIGH

Dates

Published
2022-03-02 21:33 UTC
Modified
2026-09-10 03:49 UTC

Affected packages and fixes

github.com/containerd/containerd

Go · All systems

Affected

  • introduced 0, fixed 1.4.13 (semver)

Fixed versions

1.4.13

Fix

github.com/containerd/containerd

Go · All systems

Affected

  • introduced 1.5.0, fixed 1.5.10 (semver)

Fixed versions

1.5.10

Fix

github.com/containerd/containerd

Go · All systems

Affected

  • introduced 1.6.0, fixed 1.6.1 (semver)

Fixed versions

1.6.1

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences