CVE-2020-15157containerd can be coerced into leaking credentials during image pull
- 6.1MediumCVSS base score
- 2.3%Exploitation in 30 daysEPSS · top 16% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By GitHub_M
- 4 months later
· 4 months later
Published
- 4 years later
· 4 years later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| GitHub_MCNA (assigner) | 3.1 | Medium6.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N |
| NVDNVD · Modified | 3.1 | Medium6.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N |
- EPSS (exploitation in 30 days)
- 2.3% · top 16% of all CVEs (16 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 6.1.
Affected products
- affected < 1.2.14
Affected packages
From reviewed advisories of the GitHub Advisory Database.
- Gogithub.com/containerd/containerdGHSA-742w-89gc-8m9c (opens in a new tab)
References
References5
- https://github.com/containerd/containerd/security/advisories/GHSA-742w-89gc-8m9c (opens in a new tab)x_refsource_CONFIRMx_transferred
- https://github.com/containerd/containerd/releases/tag/v1.2.14 (opens in a new tab)x_refsource_MISCx_transferred
- USN-4589-1 (opens in a new tab)vendor-advisoryx_refsource_UBUNTUx_transferred
- USN-4589-2 (opens in a new tab)vendor-advisoryx_refsource_UBUNTUx_transferred
- DSA-4865 (opens in a new tab)vendor-advisoryx_refsource_DEBIANx_transferred
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2022-0879 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisory GHSA-742w-89gc-8m9c (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2020-15157)Record last updated .