Skip to content

plugin.yaml file allows for duplicate entries in helm

Low severity GitHub Reviewed Published Sep 17, 2020 in helm/helm • Updated Oct 2, 2023

Package

gomod helm.sh/helm (Go)

Affected versions

< 2.16.11

Patched versions

2.16.11
gomod helm.sh/helm/v3 (Go)
>= 3.0.0, < 3.3.2
3.3.2

Description

Impact

During a security audit of Helm's code base, Helm maintainers identified a bug in which a Helm plugin can contain duplicates of the same entry, with the last one always used. If a plugin is compromised, this lowers the level of access that an attacker needs to modify a plugin's install hooks, causing a local execution attack.

To perform this attack, an attacker must have write access to the git repository or plugin archive (.tgz) while being downloaded (which can occur during a MITM attack on a non-SSL connection).

Patches

This issue has been patched in Helm 2.16.11 and Helm 3.3.2.

Workarounds

Make sure to install plugins using a secure connection protocol like SSL.

References

@bacongobbler bacongobbler published to helm/helm Sep 17, 2020
Published by the National Vulnerability Database Sep 17, 2020
Reviewed May 24, 2021
Published to the GitHub Advisory Database May 24, 2021
Last updated Oct 2, 2023

Severity

Low

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
Low
User interaction
Required
Scope
Changed
Confidentiality
None
Integrity
Low
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:L/UI:R/S:C/C:N/I:L/A:N

EPSS score

0.073%
(34th percentile)

CVE ID

CVE-2020-15187

GHSA ID

GHSA-c52f-pq47-2r9j

Source code

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