Repository credentials passed to alternate domain
cve-program · CVE-2021-32690
PublishedHelm 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.
Read the publisher's advisoryeuvd · EUVD-2021-1265
PublishedHelm 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.
Read the publisher's advisorynvd · CVE-2021-32690
PublishedHelm 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.
Read the publisher's advisoryosv · GHSA-56hp-xqp3-w2jf
PublishedWhile working on the Helm source, a Helm core maintainer discovered a situation where the username and password credentials associated with a Helm repository could be passed on to another domain referenced by that Helm repository. ### Impact The `index.yaml` within a Helm chart repository contains a reference where to get the chart archive for each version of a chart. The reference can be relative to the `index.yaml` file or a URL to location. The URL can point to any domain and this is a feature leveraged by Helm users. For example, an `index.yaml` file can be hosted on GitHub pages while the chart archives are hosted as GitHub releases. These are on different domain names and the `index.yaml` file points to the other domain. When a username and password were associated with a Helm repository the username and password were also passed on to other domains referenced in the `index.yaml` file. This occurred when Helm went to retrieve a specific chart archive on the other domain. ### Patches This issue has been resolved in 3.6.1. There is a slight behavior change to credential handling with regard to repositories. Usernames and passwords are only passed to the URL location of the Helm repository by default. The username and password are scoped to the scheme, host, and port of the Helm repository. To pass the username and password to other domains Helm may encounter when it goes to retrieve a chart, the new `--pass-credentials` flag can be used. This flag restores the old behavior for a single repository as an opt-in behavior. ### Workarounds If you use a username and password for a Helm repository you can 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, 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 have been passed on. ### For more information Helm's security policy is spelled out in detail in our [SECURITY](https://github.com/helm/community/blob/master/SECURITY.md) document.
Read the publisher's advisoryosv · GHSA-7jr6-prv4-5wf5
Withdrawn## Duplicate Advisory This advisory has been withdrawn because it is a duplicate of GHSA-56hp-xqp3-w2jf. This link is maintained to preserve external references. ## Original Description 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.
Read the publisher's advisoryosv · GO-2022-0384
PublishedThe username and password credentials associated with a Helm repository can be passed to another domain referenced by that Helm repository. If the index.yaml for a Helm repository is hosted on one domain and references a chart archive on a different domain, Helm will provide the credentials for the index.yaml's domain when fetching those archives.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2021-32690 · CVE overview and exploitation status
cve-program · CVE-2021-32690
- https://github.com/helm/helm/security/advisories/GHSA-56hp-xqp3-w2jf
- https://github.com/helm/helm/releases/tag/v3.6.1
euvd · EUVD-2021-1265
- https://github.com/helm/helm/security/advisories/GHSA-56hp-xqp3-w2jf
- https://github.com/helm/helm/releases/tag/v3.6.1
nvd · CVE-2021-32690
- https://github.com/helm/helm/releases/tag/v3.6.1
- https://github.com/helm/helm/security/advisories/GHSA-56hp-xqp3-w2jf
osv · GHSA-56hp-xqp3-w2jf
- https://github.com/helm/helm/security/advisories/GHSA-56hp-xqp3-w2jf
- https://nvd.nist.gov/vuln/detail/CVE-2021-32690
- https://github.com/helm/helm/commit/61d8e8c4a6f95540c15c6a65f36a6dd0a45e7a2f
- https://github.com/helm/helm
- https://github.com/helm/helm/releases/tag/v3.6.1
- https://pkg.go.dev/vuln/GO-2022-0384
osv · GHSA-7jr6-prv4-5wf5
- https://github.com/helm/helm/security/advisories/GHSA-56hp-xqp3-w2jf
- https://nvd.nist.gov/vuln/detail/CVE-2021-32690
- https://github.com/helm/helm/commit/61d8e8c4a6f95540c15c6a65f36a6dd0a45e7a2f
- https://github.com/advisories/GHSA-56hp-xqp3-w2jf
- https://github.com/helm/helm
- https://github.com/helm/helm/releases/tag/v3.6.1
- https://pkg.go.dev/vuln/GO-2022-0384
osv · GO-2022-0384
Related changes
Linked by CVE identifierNo related changes are available here.