CVE-2020-15187GHSA-C52F-PQ47-2R9JBIT-HELM-2020-15187
Duplicate plugin entries 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, 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). This issue has been patched in Helm 2.16.11 and Helm 3.3.2. As a possible workaround make sure to install plugins using a secure connection protocol like SSL.
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
From 2.0.0 · fixed in 2.16.11