Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Repository credentials passed to alternate domain

CVSS 3.1 6.8 MEDIUMEUVD CVSS 3.1 6.8 CVSS 3.1 · [email protected] · Secondary 6.8 MEDIUMCVSS 3.1 · [email protected] · Primary 8.6 HIGHCVSS 2.0 · [email protected] · Primary 5.0 MEDIUMPublisher rating MODERATEFixed by helm.sh/helm/v3 3.6.1CVSS_V3 Publisher rating MODERATEFixed by helm.sh/helm/v3 3.6.1osv · severity unknownFixed by helm.sh/helm/v3 3.6.1KEV status unknown

cve-program · CVE-2021-32690

Published

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 advisory

euvd · EUVD-2021-1265

Published

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 advisory

nvd · CVE-2021-32690

Published

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 advisory

osv · GHSA-56hp-xqp3-w2jf

Published

While 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 advisory

osv · 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 advisory

osv · GO-2022-0384

Published

The 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 advisory

Affected versions, risk and source history

cve-program · CVE-2021-32690

Published

helm

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "product": "helm",
                    "vendor": "helm",
                    "versions": [
                        {
                            "status": "affected",
                            "version": "< 3.6.1"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2021-1265

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Jun 16, 2021, 10:10:10 PM

dateUpdated: Aug 3, 2024, 11:25:31 PM

7 related source bulletins · separate from aliases

RHSA-2021:3759: Red Hat Security Advisory: OpenShift Container Platform 4.9.0 bug fix and security update

CVE-2021-3121 · CVE-2021-26539 · CVE-2021-26540 · CVE-2021-28092 · CVE-2021-29059 · CVE-2021-31525 · CVE-2021-32690 · CVE-2021-33194 · CVE-2021-33195 · CVE-2021-33197 · CVE-2021-33198 · CVE-2021-34558

msrc_CVE-2021-32690: Repository credentials passed to alternate domain

CVE-2021-32690

RHSA-2021:4902: Red Hat Security Advisory: ACS 3.67 security and enhancement update

CVE-2020-27304 · CVE-2021-3749 · CVE-2021-3801 · CVE-2021-23343 · CVE-2021-29923 · CVE-2021-32690 · CVE-2021-39293

RHSA-2021:3925: Red Hat Security Advisory: Red Hat Advanced Cluster Management 2.3.3 bug fix, security, and image updates

CVE-2021-3805 · CVE-2021-23017 · CVE-2021-23434 · CVE-2021-32626 · CVE-2021-32627 · CVE-2021-32628 · CVE-2021-32672 · CVE-2021-32675 · CVE-2021-32687 · CVE-2021-32690 · CVE-2021-41099

WID-SEC-W-2022-2339: IBM DB2: Mehrere Schwachstellen

CVE-2016-1000023 · CVE-2021-21303 · CVE-2021-32690 · CVE-2022-27664 · CVE-2022-28131 · CVE-2022-29526 · CVE-2022-30633 · CVE-2022-3172 · CVE-2022-36055 · CVE-2022-41296 · CVE-2022-41297

RHSA-2021:4618: Red Hat Security Advisory: Red Hat Advanced Cluster Management 2.4 images and security updates

CVE-2021-3711 · CVE-2021-3712 · CVE-2021-3749 · CVE-2021-23017 · CVE-2021-32626 · CVE-2021-32627 · CVE-2021-32628 · CVE-2021-32672 · CVE-2021-32675 · CVE-2021-32687 · CVE-2021-32690 · CVE-2021-32803 · CVE-2021-32804 · CVE-2021-33623 · CVE-2021-41099

RHEA-2021:3139: Red Hat Enhancement Advisory: Web Terminal 1.3 release

CVE-2021-32690

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2021-32690

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-200 · NVD-CWE-Other

Original publisher date fields

published: 2021-06-16T22:15:07.737

lastModified: 2026-06-17T03:53:25.950

1 source CPE criteria · context only
  • cpe:2.3:a:helm:helm:*:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-56hp-xqp3-w2jf

Published

helm.sh/helm/v3

Go

SEMVER · introduced 0 → fixed 3.6.1

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-7jr6-prv4-5wf5

Withdrawn

helm.sh/helm/v3

Go

SEMVER · introduced 0 → fixed 3.6.1

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GO-2022-0384

Published

helm.sh/helm/v3

Go

SEMVER · introduced 0 → fixed 3.6.1

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Nov 05:53 UTC · 273 of 275 readable · 269 fully read · documentation 469/469 current