Advisory

DEBIAN-CVE-2020-15157

Also known as: CVE-2020-15157

Summary

The record has no summary.

Details

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'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 prior, you should ensure you only pull images from trusted sources. Other container runtimes built on top of containerd but not using the default resolver (such as Docker) are not affected.

Severity

Medium Basis: CVSS v3 score 6.1, vector CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N

Dates

Published
2020-10-16 17:15 UTC
Modified
2026-10-26 12:02 UTC

Affected packages and fixes

containerd

Debian packages (deb) · Debian 12

Affected

  • introduced 0, fixed 1.3.2~ds1-2 (ecosystem)

Fixed versions

1.3.2~ds1-2

Fix

  • Fixed version 1.3.2~ds1-2
    sudo apt-get update && sudo apt-get upgrade

This command upgrades the distribution's packages. Compare the fixed version with the version you have installed.

containerd

Debian packages (deb) · Debian 13

Affected

  • introduced 0, fixed 1.3.2~ds1-2 (ecosystem)

Fixed versions

1.3.2~ds1-2

Fix

  • Fixed version 1.3.2~ds1-2
    sudo apt-get update && sudo apt-get upgrade

This command upgrades the distribution's packages. Compare the fixed version with the version you have installed.

containerd

Debian packages (deb) · Debian 14

Affected

  • introduced 0, fixed 1.3.2~ds1-2 (ecosystem)

Fixed versions

1.3.2~ds1-2

Fix

  • Fixed version 1.3.2~ds1-2
    sudo apt-get update && sudo apt-get upgrade

This command upgrades the distribution's packages. Compare the fixed version with the version you have installed.

docker.io

Debian packages (deb) · Debian 12

Affected

  • introduced 0, fixed 19.03.13+dfsg2-1 (ecosystem)

Fixed versions

19.03.13+dfsg2-1

Fix

  • Fixed version 19.03.13+dfsg2-1
    sudo apt-get update && sudo apt-get upgrade

This command upgrades the distribution's packages. Compare the fixed version with the version you have installed.

docker.io

Debian packages (deb) · Debian 13

Affected

  • introduced 0, fixed 19.03.13+dfsg2-1 (ecosystem)

Fixed versions

19.03.13+dfsg2-1

Fix

  • Fixed version 19.03.13+dfsg2-1
    sudo apt-get update && sudo apt-get upgrade

This command upgrades the distribution's packages. Compare the fixed version with the version you have installed.

docker.io

Debian packages (deb) · Debian 14

Affected

  • introduced 0, fixed 19.03.13+dfsg2-1 (ecosystem)

Fixed versions

19.03.13+dfsg2-1

Fix

  • Fixed version 19.03.13+dfsg2-1
    sudo apt-get update && sudo apt-get upgrade

This command upgrades the distribution's packages. Compare the fixed version with the version you have installed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: Debian Security Tracker (converted by OSV.dev)

Debian Security Tracker, converted to OSV by OSV.dev.

Sources & licences