https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 20:54:24 +0000 https://cve.radiocsirt.org/vuln/bdu:2021-01894 bdu:2021-01894 https://cve.radiocsirt.org/vuln/bdu:2021-01894 https://cve.radiocsirt.org/vuln/cnvd-2021-11850 cnvd-2021-11850 https://cve.radiocsirt.org/vuln/cnvd-2021-11850 https://cve.radiocsirt.org/vuln/euvd-2026-42693 EUVD-2026-42693 https://cve.radiocsirt.org/vuln/euvd-2026-42693 https://cve.radiocsirt.org/vuln/fkie_cve-2020-15157 <p>In containerd (an industry-standard container runtime) before version 1.2.14 there is a credential leaking vulnerability. If a container image manifest in the OCI Image format or Docker Image V2 Schema 2 format includes a URL for the location of a specific image layer (otherwise known as a “foreign layer”), the default containerd resolver will follow that URL to attempt to download it. In v1.2.x but not 1.3.0 or later, the default containerd resolver will provide its authentication credentials if the server where the URL is located presents an HTTP 401 status code along with registry-specific HTTP headers. If an attacker publishes a public image with a manifest that directs one of the layers to be fetched from a web server they control and they trick a user or system into pulling the image, they can obtain the credentials used for pulling that image. In some cases, this may be the user&#39;s username and password for the registry. In other cases, this may be the credentials attached to the cloud virtual instance which can grant access to other cloud resources in the account. The default containerd resolver is used by the cri-containerd plugin (which can be used by Kubernetes), the ctr development tool, and other client programs that have explicitly linked against it. This vulnerability has been fixed in containerd 1.2.14. containerd 1.3 and later are not affected. If you are using containerd 1.3 or later, you are not affected. If you are using cri-containerd in the 1.2 series or…</p> <p>In containerd (an industry-standard container runtime) before version 1.2.14 there is a credential leaking vulnerability. If a container image manifest in the OCI Image format or Docker Image V2 Schema 2 format includes a URL for the location of a specific image layer (otherwise known as a “foreign layer”), the default containerd resolver will follow that URL to attempt to download it. In v1.2.x but not 1.3.0 or later, the default containerd resolver will provide its authentication credentials if the server where the URL is located presents an HTTP 401 status code along with registry-specific HTTP headers. If an attacker publishes a public image with a manifest that directs one of the layers to be fetched from a web server they control and they trick a user or system into pulling the image, they can obtain the credentials used for pulling that image. In some cases, this may be the user&#39;s username and password for the registry. In other cases, this may be the credentials attached to the cloud virtual instance which can grant access to other cloud resources in the account. The default containerd resolver is used by the cri-containerd plugin (which can be used by Kubernetes), the ctr development tool, and other client programs that have explicitly linked against it. This vulnerability has been fixed in containerd 1.2.14. containerd 1.3 and later are not affected. If you are using containerd 1.3 or later, you are not affected. If you are using cri-containerd in the 1.2 series or…</p> https://cve.radiocsirt.org/vuln/fkie_cve-2020-15157 https://cve.radiocsirt.org/vuln/ghsa-742w-89gc-8m9c <p><strong>Affected:</strong> Go: github.com/containerd/containerd</p> <p>## Impact</p> <p>If a container image manifest in the OCI Image format or Docker Image V2 Schema 2 format includes a URL for the location of a specific image layer (otherwise known as a “foreign layer”), the default containerd resolver will follow that URL to attempt to download it. In v1.2.x but not 1.3.0 or later, the default containerd resolver will provide its authentication credentials if the server where the URL is located presents an HTTP 401 status code along with registry-specific HTTP headers.</p> <p>If an attacker publishes a public image with a manifest that directs one of the layers to be fetched from a web server they control and they trick a user or system into pulling the image, they can obtain the credentials used for pulling that image. In some cases, this may be the user&#39;s username and password for the registry. In other cases, this may be the credentials attached to the cloud virtual instance which can grant access to other cloud resources in the account.</p> <p>The default containerd resolver is used by the cri-containerd plugin (which can be used by Kubernetes), the ctr development tool, and other client programs that have explicitly linked against it.</p> <p>This vulnerability has been rated by the containerd maintainers as medium, with a CVSS score of 6.1 and a vector string of CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N.</p> <p>## Patches</p> <p>This vulnerability has been fixed in containerd 1.2.14. containerd 1.3 and later are not affected.</p> <p>## Workarounds</p> <p>If you are using contain…</p> <p><strong>Affected:</strong> Go: github.com/containerd/containerd</p> <p>## Impact</p> <p>If a container image manifest in the OCI Image format or Docker Image V2 Schema 2 format includes a URL for the location of a specific image layer (otherwise known as a “foreign layer”), the default containerd resolver will follow that URL to attempt to download it. In v1.2.x but not 1.3.0 or later, the default containerd resolver will provide its authentication credentials if the server where the URL is located presents an HTTP 401 status code along with registry-specific HTTP headers.</p> <p>If an attacker publishes a public image with a manifest that directs one of the layers to be fetched from a web server they control and they trick a user or system into pulling the image, they can obtain the credentials used for pulling that image. In some cases, this may be the user&#39;s username and password for the registry. In other cases, this may be the credentials attached to the cloud virtual instance which can grant access to other cloud resources in the account.</p> <p>The default containerd resolver is used by the cri-containerd plugin (which can be used by Kubernetes), the ctr development tool, and other client programs that have explicitly linked against it.</p> <p>This vulnerability has been rated by the containerd maintainers as medium, with a CVSS score of 6.1 and a vector string of CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N.</p> <p>## Patches</p> <p>This vulnerability has been fixed in containerd 1.2.14. containerd 1.3 and later are not affected.</p> <p>## Workarounds</p> <p>If you are using contain…</p> https://cve.radiocsirt.org/vuln/ghsa-742w-89gc-8m9c https://cve.radiocsirt.org/vuln/gsd-2020-15157 gsd-2020-15157 https://cve.radiocsirt.org/vuln/gsd-2020-15157 https://cve.radiocsirt.org/vuln/opensuse-su-2022:23018-1 <p>Security update for conmon, libcontainers-common, libseccomp, podman</p> <p>Security update for conmon, libcontainers-common, libseccomp, podman</p> https://cve.radiocsirt.org/vuln/opensuse-su-2022:23018-1 https://cve.radiocsirt.org/vuln/rhsa-2020:5634 <p>atomic-openshift: cross-namespace owner references can trigger deletions of valid children kubernetes: Ceph RBD adminSecrets exposed in logs when loglevel &gt;= 4 containerd: credentials leak during image pull python-rsa: bleichenbacher timing oracle attack against RSA decryption golang: math/big: panic during recursive division of very large numbers gogo/protobuf: plugin/unmarshal/unmarshal.go lacks certain index validation</p> <p>atomic-openshift: cross-namespace owner references can trigger deletions of valid children kubernetes: Ceph RBD adminSecrets exposed in logs when loglevel &gt;= 4 containerd: credentials leak during image pull python-rsa: bleichenbacher timing oracle attack against RSA decryption golang: math/big: panic during recursive division of very large numbers gogo/protobuf: plugin/unmarshal/unmarshal.go lacks certain index validation</p> https://cve.radiocsirt.org/vuln/rhsa-2020:5634 https://cve.radiocsirt.org/vuln/suse-su-2021:0445-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-2021:0445-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-15157 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: containerd, Ubuntu:16.04:LTS: docker.io, Ubuntu:18.04:LTS: docker.io, Ubuntu:20.04:LTS: docker.io</p> <p>In containerd (an industry-standard container runtime) before version 1.2.14 there is a credential leaking vulnerability. If a container image manifest in the OCI Image format or Docker Image V2 Schema 2 format includes a URL for the location of a specific image layer (otherwise known as a “foreign layer”), the default containerd resolver will follow that URL to attempt to download it. In v1.2.x but not 1.3.0 or later, the default containerd resolver will provide its authentication credentials if the server where the URL is located presents an HTTP 401 status code along with registry-specific HTTP headers. If an attacker publishes a public image with a manifest that directs one of the layers to be fetched from a web server they control and they trick a user or system into pulling the image, they can obtain the credentials used for pulling that image. In some cases, this may be the user&#39;s username and password for the registry. In other cases, this may be the credentials attached to the cloud virtual instance which can grant access to other cloud resources in the account. The default containerd resolver is used by the cri-containerd plugin (which can be used by Kubernetes), the ctr development tool, and other client programs that have explicitly linked against it. This vulnerability has been fixed in containerd 1.2.14. containerd 1.3 and later are not affected. If you are using containerd 1.3 or later, you are not affected. If you are using cri-containerd in the 1.2 series or…</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: containerd, Ubuntu:16.04:LTS: docker.io, Ubuntu:18.04:LTS: docker.io, Ubuntu:20.04:LTS: docker.io</p> <p>In containerd (an industry-standard container runtime) before version 1.2.14 there is a credential leaking vulnerability. If a container image manifest in the OCI Image format or Docker Image V2 Schema 2 format includes a URL for the location of a specific image layer (otherwise known as a “foreign layer”), the default containerd resolver will follow that URL to attempt to download it. In v1.2.x but not 1.3.0 or later, the default containerd resolver will provide its authentication credentials if the server where the URL is located presents an HTTP 401 status code along with registry-specific HTTP headers. If an attacker publishes a public image with a manifest that directs one of the layers to be fetched from a web server they control and they trick a user or system into pulling the image, they can obtain the credentials used for pulling that image. In some cases, this may be the user&#39;s username and password for the registry. In other cases, this may be the credentials attached to the cloud virtual instance which can grant access to other cloud resources in the account. The default containerd resolver is used by the cri-containerd plugin (which can be used by Kubernetes), the ctr development tool, and other client programs that have explicitly linked against it. This vulnerability has been fixed in containerd 1.2.14. containerd 1.3 and later are not affected. If you are using containerd 1.3 or later, you are not affected. If you are using cri-containerd in the 1.2 series or…</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-15157 https://cve.radiocsirt.org/vuln/wid-sec-w-2022-1002 <p>Ein lokaler Angreifer kann mehrere Schwachstellen in Amazon Linux 2 ausnutzen, um Informationen offenzulegen, Dateien zu manipulieren oder falsche Informationen darzustellen.</p> <p>Ein lokaler Angreifer kann mehrere Schwachstellen in Amazon Linux 2 ausnutzen, um Informationen offenzulegen, Dateien zu manipulieren oder falsche Informationen darzustellen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2022-1002