CVE-2020-15185

Specific Go Packages Affected

helm.sh/helm/v3/pkg/repo

Workarounds

• do not install charts from repositories you do not trust
• fetch charts using a secure channel of communication (such as TLS)
• use helm pull to fetch the chart, then review the chart’s content (either manually, or with helm verify if it has been signed) to ensure it has not been tampered with
• manually review the index file in the Helm repository cache before installing software.

During a security audit of Helm's code base, security researchers at Trail of Bits identified a bug in which the a Helm repository can contain duplicates of the same chart, with the last one always used. If a repository is compromised, this lowers the level of access that an attacker needs to inject a bad chart into a repository.

To perform this attack, an attacker must have write access to the index file (which can occur during a MITM attack on a non-SSL connection).

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

CVE-2020-15185 has a CVSS score of 2.2 (Low). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.3.2, 2.16.11); upgrading removes the vulnerable code path.

Kodem intelligence

This issue has been patched in Helm 3.3.2 and 2.16.11

1. What is CVE-2020-15185? CVE-2020-15185 is a low-severity improper input validation vulnerability in helm.sh/helm/v3 (go), affecting versions >= 3.0.0, < 3.3.2. It is fixed in 3.3.2, 2.16.11. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
2. How severe is CVE-2020-15185? CVE-2020-15185 has a CVSS score of 2.2 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2020-15185?
   • helm.sh/helm/v3 (go) (versions >= 3.0.0, < 3.3.2)
   • helm.sh/helm (go) (versions < 2.16.11)
4. Is there a fix for CVE-2020-15185? Yes. CVE-2020-15185 is fixed in 3.3.2, 2.16.11. Upgrade to this version or later.
5. Is CVE-2020-15185 exploitable, and should I be worried? Whether CVE-2020-15185 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2020-15185 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2020-15185?
   • Upgrade helm.sh/helm/v3 to 3.3.2 or later
   • Upgrade helm.sh/helm to 2.16.11 or later