Insufficiently protected credentials in containerd - CVE-2020-15157

Vulnerability details

The vulnerability allows a remote attacker to gain access to sensitive information.

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 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'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.

Affected software

How to mitigate CVE-2020-15157

External References

• https://github.com/containerd/containerd/releases/tag/v1.2.14
• https://github.com/containerd/containerd/security/advisories/GHSA-742w-89gc-8m9c

Related Security Bulletins

• Information disclosure in containerd
• Amazon Linux AMI update for containerd
• Debian update for docker.io
• Amazon Linux AMI update for containerd
• SUSE update for libcontainers-common
• Ubuntu update for docker.io
• Ubuntu update for containerd
• Fedora EPEL 7 update for containerd