Helm is a tool for managing Charts (packages of pre-configured Kubernetes resources). In versions of helm prior to 3.6.1, a vulnerability exists where the username and password credentials associated with a Helm repository could be passed on to another domain referenced by that Helm repository. This issue has been resolved in 3.6.1. There is a workaround through which one may check for improperly passed credentials. One may use a username and password for a Helm repository and may audit the Helm repository in order to check for another domain being used that could have received the credentials. In the index.yaml file for that repository, one may look for another domain in the urls list for the chart versions. If there is another domain found and that chart version was pulled or installed, the credentials would be passed on.
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 |
|---|---|---|---|
| Helm | Helm | * | 3.6.1 (excluding) |
| Red Hat Advanced Cluster Management for Kubernetes 2.3 for RHEL 8 | RedHat | rhacm2/multicluster-operators-channel-rhel8:v2.3.3-2 | * |
| Red Hat OpenShift Container Platform 4.9 | RedHat | openshift4/ose-console:v4.9.0-202110130449.p0.git.8c077e4.assembly.rc.8 | * |
| RHACS-3.67-RHEL-8 | RedHat | advanced-cluster-security/rhacs-rhel8-operator:3.67.0-3 | * |
| RHEL-8 based Middleware Containers | RedHat | web-terminal-tech-preview/web-terminal-exec-rhel8:1.3-9 | * |
| RHEL-8 based Middleware Containers | RedHat | web-terminal-tech-preview/web-terminal-rhel8-operator:1.3-20 | * |
| RHEL-8 based Middleware Containers | RedHat | web-terminal-tech-preview/web-terminal-rhel8-operator-metadata:1.3-19 | * |
| RHEL-8 based Middleware Containers | RedHat | web-terminal-tech-preview/web-terminal-tooling-rhel8:1.3-6 | * |
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.