Insufficiently Protected Credentials Affecting docker.io package, versions <19.03.13+dfsg2-1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-DEBIANUNSTABLE-DOCKERIO-1022024
- published16 Oct 2020
- disclosed16 Oct 2020
Introduced: 16 Oct 2020
CVE-2020-15157 (opens in a new tab)How to fix?
Upgrade Debian:unstable docker.io to version 19.03.13+dfsg2-1 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream docker.io package and not the docker.io package as distributed by Debian.
See How to fix? for Debian:unstable relevant fixed versions and status.
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.
References
- https://security-tracker.debian.org/tracker/CVE-2020-15157
- https://github.com/containerd/containerd/security/advisories/GHSA-742w-89gc-8m9c
- https://www.debian.org/security/2021/dsa-4865
- https://github.com/containerd/containerd/releases/tag/v1.2.14
- https://usn.ubuntu.com/4589-1/
- https://usn.ubuntu.com/4589-2/