containerd can be coerced into leaking credentials during image pull
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
cve-program · CVE-2020-15157
PublishedIn 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.
- Source published
- 16 Oct 2020 16:45:18 UTC
- Source modified
- 4 Aug 2024 13:08:22 UTC
- Saved here
- 23 Oct 2026 15:48:27 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · 6.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N
euvd · EUVD-2022-0879
PublishedIn 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.
Additional publisher context
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Oct 16, 2020, 4:45:18 PM
dateUpdated: Aug 4, 2024, 1:08:22 PM
8 related source bulletins · separate from aliases
openSUSE-SU-2024:10693-1: containerd-1.4.8-2.2 on GA media
CVE-2016-9962 · CVE-2018-16873 · CVE-2018-16874 · CVE-2018-16875 · CVE-2019-5736 · CVE-2020-15157 · CVE-2020-15257 · CVE-2021-21334 · CVE-2021-32760
SUSE-SU-2021:0445-1: Security update for containerd, docker, docker-runc, golang-github-docker-libnetwork
CVE-2020-15157 · CVE-2021-21284 · CVE-2021-21285
openSUSE-SU-2024:11757-1: libcontainers-common-20210626-7.1 on GA media
CVE-2020-14370 · CVE-2020-15157 · CVE-2021-20199 · CVE-2021-20291 · CVE-2021-3602
RHSA-2020:5634: Red Hat Security Advisory: OpenShift Container Platform 4.7.0 packages security update
CVE-2019-3884 · CVE-2020-8566 · CVE-2020-15157 · CVE-2020-25658 · CVE-2020-28362 · CVE-2021-3121
SUSE-SU-2022:23018-1: Security update for conmon, libcontainers-common, libseccomp, podman
CVE-2020-14370 · CVE-2020-15157 · CVE-2021-20199 · CVE-2021-20291 · CVE-2021-3602 · CVE-2021-4024 · CVE-2021-41190
openSUSE-SU-2022:23018-1: Security update for conmon, libcontainers-common, libseccomp, podman
CVE-2020-14370 · CVE-2020-15157 · CVE-2021-20199 · CVE-2021-20291 · CVE-2021-3602 · CVE-2021-4024 · CVE-2021-41190
WID-SEC-W-2022-1002: Amazon Linux 2: Mehrere Schwachstellen
CVE-2021-21334 · CVE-2021-32760 · CVE-2021-41190 · CVE-2020-15157
SUSE-SU-2022:3312-1: Security update for libcontainers-common
CVE-2020-14370 · CVE-2020-15157 · CVE-2021-20199 · CVE-2021-20291 · CVE-2021-3602
- Source published
- Oct 16, 2020, 4:45:18 PM (timezone not stated)
- Source modified
- Aug 4, 2024, 1:08:22 PM (timezone not stated)
- Saved here
- 17 Nov 2026 22:44:09 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
EUVD CVSS 3.1 · 6.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N
nvd · CVE-2020-15157
PublishedIn 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.
Additional publisher context
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Modified
Weakness classifications: CWE-522
Original publisher date fields
published: 2020-10-16T17:15:11.870
lastModified: 2026-06-17T02:56:09.850
13 source CPE criteria · context only
- cpe:2.3:a:linuxfoundation:containerd:*:*:*:*:*:*:*:*
- cpe:2.3:a:linuxfoundation:containerd:1.3.0:-:*:*:*:*:*:*
- cpe:2.3:a:linuxfoundation:containerd:1.3.0:beta0:*:*:*:*:*:*
- cpe:2.3:a:linuxfoundation:containerd:1.3.0:beta1:*:*:*:*:*:*
- cpe:2.3:a:linuxfoundation:containerd:1.3.0:beta2:*:*:*:*:*:*
- cpe:2.3:a:linuxfoundation:containerd:1.3.0:rc0:*:*:*:*:*:*
- cpe:2.3:a:linuxfoundation:containerd:1.3.0:rc1:*:*:*:*:*:*
- cpe:2.3:a:linuxfoundation:containerd:1.3.0:rc2:*:*:*:*:*:*
- cpe:2.3:a:linuxfoundation:containerd:1.3.0:rc3:*:*:*:*:*:*
- cpe:2.3:o:canonical:ubuntu_linux:16.04:*:*:*:lts:*:*:*
- cpe:2.3:o:canonical:ubuntu_linux:18.04:*:*:*:lts:*:*:*
- cpe:2.3:o:canonical:ubuntu_linux:20.04:*:*:*:lts:*:*:*
- cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
- Source published
- 16 Oct 2020 17:15:11 UTC
- Source modified
- 17 Jun 2026 02:56:09 UTC
- Saved here
- 24 Oct 2026 16:17:26 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · [email protected] · Secondary · 6.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N
CVSS 3.1 · [email protected] · Primary · 6.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N
CVSS 2.0 · [email protected] · Primary · 2.6 AV:N/AC:H/Au:N/C:P/I:N/A:N
osv · GHSA-742w-89gc-8m9c
Published## Impact 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 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. ## Patches This vulnerability has been fixed in containerd 1.2.14. containerd 1.3 and later are not affected. ## Workarounds 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. ## Credits The containerd maintainers would like to thank Brad Geesaman, Josh Larsen, Ian Coldwater, Duffie Cooley, and Rory McCune for responsibly disclosing this issue in accordance with the [containerd security policy](https://github.com/containerd/project/blob/master/SECURITY.md).
- Source published
- 11 Feb 2022 23:27:39 UTC
- Source modified
- 10 Sep 2026 03:49:11 UTC
- Saved here
- 24 Oct 2026 13:19:41 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V3 · CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N
Publisher rating · MODERATE
osv · GO-2022-0803
Publishedcontainerd v1.2.x can be coerced into leaking credentials during image pull in github.com/containerd/containerd
- Source published
- 21 Aug 2024 15:29:02 UTC
- Source modified
- 3 Mar 2026 04:50:52 UTC
- Saved here
- 24 Oct 2026 13:19:41 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.