CVE-2020-15157

Published: 15 October 2020

If a container image manifest in the Image V2 Schema 2 format includes a URL for the location of a specific image layer, ctr/containerd will follow that URL to attempt to download it. In v1.2.x but not 1.3.x, ctr/containerd 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 by ctr/containerd. 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.

Priority

Medium

CVSS 3 base score: 6.1

Status

Package Release Status
containerd
Launchpad, Ubuntu, Debian
Upstream Needs triage

Ubuntu 20.10 (Groovy Gorilla) Not vulnerable
(v1.2 only)
Ubuntu 20.04 LTS (Focal Fossa) Not vulnerable
(v1.2 only)
Ubuntu 18.04 LTS (Bionic Beaver) Not vulnerable
(v1.2 only)
Ubuntu 16.04 LTS (Xenial Xerus)
Released (1.2.6-0ubuntu1~16.04.4)
Ubuntu 14.04 ESM (Trusty Tahr) Does not exist

Ubuntu 12.04 ESM (Precise Pangolin) Does not exist

docker.io
Launchpad, Ubuntu, Debian
Upstream Needs triage

Ubuntu 20.10 (Groovy Gorilla)
Released (19.03.13-0ubuntu3)
Ubuntu 20.04 LTS (Focal Fossa)
Released (19.03.8-0ubuntu1.20.04.1)
Ubuntu 18.04 LTS (Bionic Beaver)
Released (19.03.6-0ubuntu1~18.04.2)
Ubuntu 16.04 LTS (Xenial Xerus)
Released (18.09.7-0ubuntu1~16.04.6)
Ubuntu 14.04 ESM (Trusty Tahr) Does not exist

Ubuntu 12.04 ESM (Precise Pangolin) Does not exist