CVE-2020-15157Medium· 6.1▾ Sunlitcontainerd v1.2.x can be coerced into leaking credentials during image pull
▾ Sunlit zone — Low / medium · no exploitation signal
impact 33.6 · likelihood 0.5 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Sep 12.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
2.3%
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.
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.
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.
github.com/containerd/containerd < 1.2.14Upgrade to a patched release:
github.com/containerd/containerd 1.2.14Connected by shared product, vendor, weakness, or advisory.
GHSA-7ww5-4wqc-m92cMediumcontainerd allows RAPL to be accessible to a container
GHSA-5j5w-g665-5m35Low· 3.0Ambiguous OCI manifest parsing
CVE-2022-31030Medium· 5.5containerd CRI plugin: Host memory exhaustion through ExecSync
CVE-2020-15257Medium· 5.2containerd-shim API Exposed to Host Network Containers
CVE-2022-23471Medium· 5.7containerd CRI stream server vulnerable to host memory exhaustion via terminal
CVE-2021-43816High· 8.0Unprivileged pod using `hostPath` can side-step active LSM when it is SELinux