In containerd (an industry-standard container runtime) before versions 1.3.10 and 1.4.4, containers launched through containerds CRI implementation (through Kubernetes, crictl, or any other pod/container client that uses the containerd CRI service) that share the same image may receive incorrect environment variables, including values that are defined for other containers. If the affected containers have different security contexts, this may allow sensitive information to be unintentionally shared. If you are not using containerds CRI implementation (through one of the mechanisms described above), you are not vulnerable to this issue. If you are not launching multiple containers or Kubernetes pods from the same image which have different environment variables, you are not vulnerable to this issue. If you are not launching multiple containers or Kubernetes pods from the same image in rapid succession, you have reduced likelihood of being vulnerable to this issue This vulnerability has been fixed in containerd 1.3.10 and containerd 1.4.4. Users should update to these versions.
The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Containerd | Linuxfoundation | * | 1.3.10 (excluding) |
| Containerd | Linuxfoundation | 1.4.0 (including) | 1.4.4 (excluding) |
| Containerd | Ubuntu | bionic | * |
| Containerd | Ubuntu | devel | * |
| Containerd | Ubuntu | esm-apps/xenial | * |
| Containerd | Ubuntu | focal | * |
| Containerd | Ubuntu | groovy | * |
| Containerd | Ubuntu | hirsute | * |
| Containerd | Ubuntu | impish | * |
| Containerd | Ubuntu | jammy | * |
| Containerd | Ubuntu | kinetic | * |
| Containerd | Ubuntu | lunar | * |
| Containerd | Ubuntu | mantic | * |
| Containerd | Ubuntu | noble | * |
| Containerd | Ubuntu | oracular | * |
| Containerd | Ubuntu | trusty | * |
| Containerd | Ubuntu | upstream | * |
| Containerd | Ubuntu | xenial | * |
Resources such as files and directories may be inadvertently exposed through mechanisms such as insecure permissions, or when a program accidentally operates on the wrong object. For example, a program may intend that private files can only be provided to a specific user. This effectively defines a control sphere that is intended to prevent attackers from accessing these private files. If the file permissions are insecure, then parties other than the user will be able to access those files. A separate control sphere might effectively require that the user can only access the private files, but not any other files on the system. If the program does not ensure that the user is only requesting private files, then the user might be able to access other files on the system. In either case, the end result is that a resource has been exposed to the wrong party.