CVE-2020-15184GHSA-9VP5-M38W-J776BIT-HELM-2020-15184
Aliases are never checked in Helm
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.16.11, 3.3.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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 information into a chart. This issue has been patched in Helm 3.3.2 and 2.16.11. A possible workaround is to 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.
Timeline
- CVE published
- Record last updated
Affected versions
- helm helm
From 2.0.0 · fixed in 2.16.11; From 3.0.0 · fixed in 3.3.2
- helm.sh/helm/v3Go
From 3.0.0 · fixed in 3.3.2
- helm.sh/helmGo
fixed in 2.16.11