Skip to content

Helm dependency management path traversal

Moderate severity GitHub Reviewed Published Feb 14, 2024 in helm/helm • Updated Feb 15, 2024

Package

gomod helm.sh/helm/v3 (Go)

Affected versions

<= 3.14.0

Patched versions

3.14.1

Description

A Helm contributor discovered a path traversal vulnerability when Helm saves a chart including at download time.

Impact

When either the Helm client or SDK is used to save a chart whose name within the Chart.yaml file includes a relative path change, the chart would be saved outside its expected directory based on the changes in the relative path. The validation and linting did not detect the path changes in the name.

Patches

This issue has been resolved in Helm v3.14.1.

Workarounds

Check all charts used by Helm for path changes in their name as found in the Chart.yaml file. This includes dependencies.

Credits

Disclosed by Dominykas Blyžė at Nearform Ltd.

References

@mattfarina mattfarina published to helm/helm Feb 14, 2024
Published by the National Vulnerability Database Feb 15, 2024
Published to the GitHub Advisory Database Feb 15, 2024
Reviewed Feb 15, 2024
Last updated Feb 15, 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
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
Low
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:L/PR:L/UI:N/S:C/C:L/I:L/A:N

EPSS score

0.044%
(11th percentile)

Weaknesses

CVE ID

CVE-2024-25620

GHSA ID

GHSA-v53g-5gjp-272r

Source code

Credits

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