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.
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Containerd | Linuxfoundation | * | 1.4.13 (excluding) |
| Containerd | Linuxfoundation | 1.5.0 (including) | 1.5.10 (excluding) |
| Containerd | Linuxfoundation | 1.6.0 (including) | 1.6.1 (excluding) |
| Containerd | Ubuntu | bionic | * |
| Containerd | Ubuntu | devel | * |
| Containerd | Ubuntu | esm-apps/xenial | * |
| Containerd | Ubuntu | focal | * |
| Containerd | Ubuntu | impish | * |
| Containerd | Ubuntu | jammy | * |
| Containerd | Ubuntu | upstream | * |
| Containerd | Ubuntu | xenial | * |
There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include:
Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include:
Information exposures can occur in different ways:
It is common practice to describe any loss of confidentiality as an “information exposure,” but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read. CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.