https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 14:13:08 +0000 https://cve.radiocsirt.org/vuln/bdu:2021-01907 bdu:2021-01907 https://cve.radiocsirt.org/vuln/bdu:2021-01907 https://cve.radiocsirt.org/vuln/bell-cve-2020-15257 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Withdrawn by the publisher.</strong></p> https://cve.radiocsirt.org/vuln/bell-cve-2020-15257 https://cve.radiocsirt.org/vuln/certfr-2022-avi-624 certfr-2022-avi-624 https://cve.radiocsirt.org/vuln/certfr-2022-avi-624 https://cve.radiocsirt.org/vuln/cleanstart-2025-ia92737 <p><strong>Affected:</strong> CleanStart: containerd</p> <p>Security vulnerability affects the containerd package. containerd is an industry-standard container runtime and is available as a daemon for Linux and Windows.</p> <p><strong>Affected:</strong> CleanStart: containerd</p> <p>Security vulnerability affects the containerd package. containerd is an industry-standard container runtime and is available as a daemon for Linux and Windows.</p> https://cve.radiocsirt.org/vuln/cleanstart-2025-ia92737 https://cve.radiocsirt.org/vuln/euvd-2026-42808 EUVD-2026-42808 https://cve.radiocsirt.org/vuln/euvd-2026-42808 https://cve.radiocsirt.org/vuln/fkie_cve-2020-15257 <p>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 &#34;host&#34; 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…</p> <p>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 &#34;host&#34; 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…</p> https://cve.radiocsirt.org/vuln/fkie_cve-2020-15257 https://cve.radiocsirt.org/vuln/ghsa-36xw-fx78-c5r4 <p><strong>Affected:</strong> Go: github.com/containerd/containerd</p> <p>## Impact</p> <p>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.</p> <p>### Specific Go Packages Affected github.com/containerd/containerd/cmd</p> <p>## Patches</p> <p>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.</p> <p>## Workarounds</p> <p>If you are not providing the ability for untrusted users to start containers in the same network namespace as the shim (typically the &#34;host&#34; 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.</p> <p>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.</p> <p>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 adv…</p> <p><strong>Affected:</strong> Go: github.com/containerd/containerd</p> <p>## Impact</p> <p>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.</p> <p>### Specific Go Packages Affected github.com/containerd/containerd/cmd</p> <p>## Patches</p> <p>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.</p> <p>## Workarounds</p> <p>If you are not providing the ability for untrusted users to start containers in the same network namespace as the shim (typically the &#34;host&#34; 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.</p> <p>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.</p> <p>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 adv…</p> https://cve.radiocsirt.org/vuln/ghsa-36xw-fx78-c5r4 https://cve.radiocsirt.org/vuln/gsd-2020-15257 gsd-2020-15257 https://cve.radiocsirt.org/vuln/gsd-2020-15257 https://cve.radiocsirt.org/vuln/opensuse-su-2021:0278-1 <p>Security update for containerd, docker, docker-runc, golang-github-docker-libnetwork</p> <p>Security update for containerd, docker, docker-runc, golang-github-docker-libnetwork</p> https://cve.radiocsirt.org/vuln/opensuse-su-2021:0278-1 https://cve.radiocsirt.org/vuln/rhsa-2022:2183 <p>kubernetes: YAML parsing vulnerable to &#34;Billion Laughs&#34; attack, allowing for remote denial of service golang-github-miekg-dns: predictable TXID can lead to response forgeries containerd: unrestricted access to abstract Unix domain socket can lead to privileges escalation ulikunitz/xz: Infinite loop in readUvarint allows for denial of service containerd: pulling and extracting crafted container image may result in Unix file permission changes</p> <p>kubernetes: YAML parsing vulnerable to &#34;Billion Laughs&#34; attack, allowing for remote denial of service golang-github-miekg-dns: predictable TXID can lead to response forgeries containerd: unrestricted access to abstract Unix domain socket can lead to privileges escalation ulikunitz/xz: Infinite loop in readUvarint allows for denial of service containerd: pulling and extracting crafted container image may result in Unix file permission changes</p> https://cve.radiocsirt.org/vuln/rhsa-2022:2183 https://cve.radiocsirt.org/vuln/suse-su-2020:3938-1 <p>Security update for containerd, docker, docker-runc, golang-github-docker-libnetwork</p> <p>Security update for containerd, docker, docker-runc, golang-github-docker-libnetwork</p> https://cve.radiocsirt.org/vuln/suse-su-2020:3938-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-15257 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: containerd, Ubuntu:18.04:LTS: containerd, Ubuntu:20.04:LTS: containerd</p> <p>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 &#34;host&#34; 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…</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: containerd, Ubuntu:18.04:LTS: containerd, Ubuntu:20.04:LTS: containerd</p> <p>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 &#34;host&#34; 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…</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-15257 https://cve.radiocsirt.org/vuln/wid-sec-w-2023-2947 <p>Ein entfernter, authentisierter Angreifer kann eine Schwachstelle in docker und Kubernetes ausnutzen, um seine Privilegien zu erhöhen.</p> <p>Ein entfernter, authentisierter Angreifer kann eine Schwachstelle in docker und Kubernetes ausnutzen, um seine Privilegien zu erhöhen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2023-2947