VulnerableCode Package Details - pkg:alpm/archlinux/containerd@1.4.3-1

Search for packages

Vulnerability	Summary	Fixed by
VCID-fwws-cz11-aaag Aliases: CVE-2021-21334 GHSA-6g2q-w5j3-fwh4	In containerd (an industry-standard container runtime) before versions 1.3.10 and 1.4.4, containers launched through containerd's 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 containerd's 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.	1.4.4-1 Affected by 0 other vulnerabilities.

Vulnerability

Summary

Fixed by

VCID-fwws-cz11-aaag
Aliases:
CVE-2021-21334
GHSA-6g2q-w5j3-fwh4

In containerd (an industry-standard container runtime) before versions 1.3.10 and 1.4.4, containers launched through containerd's 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 containerd's 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.

1.4.4-1
Affected by 0 other vulnerabilities.

Vulnerability	Summary	Aliases
VCID-y9hs-1kk2-aaam	containerd is an industry-standard container runtime and is available as a daemon for Linux and Windows. In containerd before versions 1.3.9 and 1.4.3, the containerd-shim API is improperly exposed to host network containers. Access controls for the shim’s API socket verified that the connecting process had an effective UID of 0, but did not otherwise restrict access to the abstract Unix domain socket. This would allow malicious containers running in the same network namespace as the shim, with an effective UID of 0 but otherwise reduced privileges, to cause new processes to be run with elevated privileges. This vulnerability has been fixed in containerd 1.3.9 and 1.4.3. Users should update to these versions as soon as they are released. It should be noted that containers started with an old version of containerd-shim should be stopped and restarted, as running containers will continue to be vulnerable even after an upgrade. If you are not providing the ability for untrusted users to start containers in the same network namespace as the shim (typically the "host" network namespace, for example with docker run --net=host or hostNetwork: true in a Kubernetes pod) and run with an effective UID of 0, you are not vulnerable to this issue. If you are running containers with a vulnerable configuration, you can deny access to all abstract sockets with AppArmor by adding a line similar to deny unix addr=@**, to your policy. It is best practice to run containers with a reduced set of privileges, with a non-zero UID, and with isolated namespaces. The containerd maintainers strongly advise against sharing namespaces with the host. Reducing the set of isolation mechanisms used for a container necessarily increases that container's privilege, regardless of what container runtime is used for running that container.	CVE-2020-15257 GHSA-36xw-fx78-c5r4

Vulnerability

Summary

Aliases

VCID-y9hs-1kk2-aaam

containerd is an industry-standard container runtime and is available as a daemon for Linux and Windows. In containerd before versions 1.3.9 and 1.4.3, the containerd-shim API is improperly exposed to host network containers. Access controls for the shim’s API socket verified that the connecting process had an effective UID of 0, but did not otherwise restrict access to the abstract Unix domain socket. This would allow malicious containers running in the same network namespace as the shim, with an effective UID of 0 but otherwise reduced privileges, to cause new processes to be run with elevated privileges. This vulnerability has been fixed in containerd 1.3.9 and 1.4.3. Users should update to these versions as soon as they are released. It should be noted that containers started with an old version of containerd-shim should be stopped and restarted, as running containers will continue to be vulnerable even after an upgrade. If you are not providing the ability for untrusted users to start containers in the same network namespace as the shim (typically the "host" network namespace, for example with docker run --net=host or hostNetwork: true in a Kubernetes pod) and run with an effective UID of 0, you are not vulnerable to this issue. If you are running containers with a vulnerable configuration, you can deny access to all abstract sockets with AppArmor by adding a line similar to deny unix addr=@**, to your policy. It is best practice to run containers with a reduced set of privileges, with a non-zero UID, and with isolated namespaces. The containerd maintainers strongly advise against sharing namespaces with the host. Reducing the set of isolation mechanisms used for a container necessarily increases that container's privilege, regardless of what container runtime is used for running that container.

CVE-2020-15257
GHSA-36xw-fx78-c5r4

Date	Actor	Action	Vulnerability	Source	VulnerableCode Version
2025-03-28T07:46:41.490056+00:00	Arch Linux Importer	Affected by	VCID-fwws-cz11-aaag	https://security.archlinux.org/AVG-1650	36.0.0
2025-03-28T07:45:47.486050+00:00	Arch Linux Importer	Fixing	VCID-y9hs-1kk2-aaam	https://security.archlinux.org/AVG-1309	36.0.0
2024-09-18T02:02:02.267473+00:00	Arch Linux Importer	Affected by	VCID-fwws-cz11-aaag	https://security.archlinux.org/AVG-1650	34.0.1
2024-09-18T02:00:48.892732+00:00	Arch Linux Importer	Fixing	VCID-y9hs-1kk2-aaam	https://security.archlinux.org/AVG-1309	34.0.1
2024-01-12T19:57:53.136303+00:00	Arch Linux Importer	Fixing	VCID-y9hs-1kk2-aaam	https://security.archlinux.org/AVG-1309	34.0.0rc2
2024-01-03T22:28:05.176322+00:00	Arch Linux Importer	Affected by	VCID-fwws-cz11-aaag	https://security.archlinux.org/AVG-1650	34.0.0rc1
2024-01-03T22:27:06.616997+00:00	Arch Linux Importer	Fixing	VCID-y9hs-1kk2-aaam	https://security.archlinux.org/AVG-1309	34.0.0rc1