CVE-2020-15184

Aliases are never checked in Helm

LOW
2.7
CVSS Score
Published: September 17, 2020 at 08:40 PM UTC
Updated: June 17, 2026 at 02:56 AM UTC
1 product affected across 1 vendorHelm

Using helm by helm?

Get instant alerts when new vulnerabilities affect helm - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
LOW2.7
Exploit prediction
EPSS 1%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 2.16.11v < 3.3.22.0.0 ≤ v < 2.16.113.0.0 ≤ v < 3.3.2
Affected range stops below 2.16.11, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.3.2, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
HIGH
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
LOW
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-20CWE-74

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card