containerd is a container runtime. A bug was found in containerd versions prior to 1.4.8 and 1.5.4 where pulling and extracting a specially-crafted container image can result in Unix file permission changes for existing files in the host’s filesystem. Changes to file permissions can deny access to the expected owner of the file, widen access to others, or set extended bits like setuid, setgid, and sticky. This bug does not directly allow files to be read, modified, or executed without an additional cooperating process. This bug has been fixed in containerd 1.5.4 and 1.4.8. As a workaround, ensure that users only pull images from trusted sources. Linux security modules (LSMs) like SELinux and AppArmor can limit the files potentially affected by this bug through policies and profiles that prevent containerd from interacting with specific files.
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.4.8 (excluding) |
| Containerd | Linuxfoundation | 1.5.0 (including) | 1.5.4 (excluding) |
| Red Hat OpenShift Service Mesh 2.4 for RHEL 8 | RedHat | openshift-service-mesh/grafana-rhel8:2.4.4-2 | * |
| Red Hat OpenShift Service Mesh 2.4 for RHEL 8 | RedHat | openshift-service-mesh/istio-cni-rhel8:2.4.4-5 | * |
| Red Hat OpenShift Service Mesh 2.4 for RHEL 8 | RedHat | openshift-service-mesh/istio-must-gather-rhel8:2.4.4-3 | * |
| Red Hat OpenShift Service Mesh 2.4 for RHEL 8 | RedHat | openshift-service-mesh/istio-rhel8-operator:2.4.4-6 | * |
| Red Hat OpenShift Service Mesh 2.4 for RHEL 8 | RedHat | openshift-service-mesh/kiali-rhel8:1.65.9-4 | * |
| Red Hat OpenShift Service Mesh 2.4 for RHEL 8 | RedHat | openshift-service-mesh/kiali-rhel8-operator:1.65.9-1 | * |
| Red Hat OpenShift Service Mesh 2.4 for RHEL 8 | RedHat | openshift-service-mesh/pilot-rhel8:2.4.4-5 | * |
| Red Hat OpenShift Service Mesh 2.4 for RHEL 8 | RedHat | openshift-service-mesh/proxyv2-rhel8:2.4.4-5 | * |
| Red Hat OpenShift Service Mesh 2.4 for RHEL 8 | RedHat | openshift-service-mesh/ratelimit-rhel8:2.4.4-2 | * |
| Red Hat OpenStack Platform 16.2 | RedHat | rhosp-rhel8-tech-preview/osp-director-operator:1.2.3-2 | * |
| 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 | 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.