Skip to content

Duplicate Advisory: Helm passes repository credentials to alternate domain

Moderate severity GitHub Reviewed Published Jun 23, 2021 to the GitHub Advisory Database • Updated May 20, 2024
Withdrawn This advisory was withdrawn on May 20, 2024

Package

gomod helm.sh/helm/v3 (Go)

Affected versions

< 3.6.1

Patched versions

3.6.1

Description

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.

References

Published by the National Vulnerability Database Jun 16, 2021
Reviewed Jun 18, 2021
Published to the GitHub Advisory Database Jun 23, 2021
Last updated May 20, 2024
Withdrawn May 20, 2024

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N

Weaknesses

CVE ID

No known CVE

GHSA ID

GHSA-7jr6-prv4-5wf5

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.