First published: Wed Feb 14 2024(Updated: )
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.
Credit: security-advisories@github.com security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
go/helm.sh/helm/v3 | <=3.14.0 | 3.14.1 |
redhat/helm | <3.14.1 | 3.14.1 |
Helm | <3.14.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-25620 is classified as a medium severity vulnerability.
To fix CVE-2024-25620, update Helm to version 3.14.1 or later.
The impact of CVE-2024-25620 is that it allows path traversal when saving a chart with a relative path in the Chart.yaml file.
Versions of Helm prior to 3.14.1 are affected by CVE-2024-25620.
Yes, CVE-2024-25620 affects the Helm client and SDK when saving charts.