Docker CLI is the command line interface for the docker container runtime. A bug was found in the Docker CLI where running docker login my-private-registry.example.com with a misconfigured configuration file (typically ~/.docker/config.json) listing a credsStore or credHelpers that could not be executed would result in any provided credentials being sent to registry-1.docker.io rather than the intended private registry. This bug has been fixed in Docker CLI 20.10.9. Users should update to this version as soon as possible. For users unable to update ensure that any configured credsStore or credHelpers entries in the configuration file reference an installed credential helper that is executable and on the PATH.
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Command_line_interface | Docker | * | 20.10.9 (excluding) |
| Docker.io | Ubuntu | bionic | * |
| Docker.io | Ubuntu | devel | * |
| Docker.io | Ubuntu | esm-apps/xenial | * |
| Docker.io | Ubuntu | focal | * |
| Docker.io | Ubuntu | hirsute | * |
| Docker.io | Ubuntu | impish | * |
| Docker.io | Ubuntu | jammy | * |
| Docker.io | Ubuntu | kinetic | * |
| Docker.io | Ubuntu | lunar | * |
| Docker.io | Ubuntu | mantic | * |
| Docker.io | Ubuntu | noble | * |
| Docker.io | Ubuntu | oracular | * |
| Docker.io | Ubuntu | trusty | * |
| Docker.io | Ubuntu | upstream | * |
| Docker.io | Ubuntu | xenial | * |
There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include:
Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include:
Information exposures can occur in different ways:
It is common practice to describe any loss of confidentiality as an “information exposure,” but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read. CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.