Aliases are never checked in helm
### Impact During a security audit of Helm's code base, security researchers at Trail of Bits identified a bug in which the `alias` field on a `Chart.yaml` is not properly sanitized. This could lead to the injection of unwanted information into a chart. ### Patches This issue has been patched in Helm 3.3.2 and 2.16.11 ### Specific Go Packages Affected helm.sh/helm/v3/pkg/chartutil ### Workarounds Manually review the `dependencies` field of any untrusted chart, verifying that the `alias` field is either not used, or (if used) does not contain newlines or path characters.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2020-15184US | low2.7 | — | ||
In Helm before versions 2.16.11 and 3.3.2 there is a bug in which the `alias` field on a `Chart.yaml` is not properly sanitized. This could lead to the injection of unwanted inform… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/helm/helmPACKAGE
- https://github.com/helm/helm/commit/6aab63765f99050b115f0aec3d6350c85e8da946WEB
- https://github.com/helm/helm/commit/e7c281564d8306e1dcf8023d97f972449ad74850WEB
- https://github.com/helm/helm/security/advisories/GHSA-9vp5-m38w-j776WEB
- https://nvd.nist.gov/vuln/detail/CVE-2020-15184ADVISORY
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan