CVE-2020-15184
helm: Chart.yaml is not properly sanitized lead to injection of unwanted information into chart
Overview
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.
Source: OX vulnerability database
Severity
2.7 · LOW
CVSS 3.1 base score, scored by NVD.
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N
Weakness: CWE-20, CWE-74
Affected packages · 3
| Ecosystem | Package | Vulnerable | Fixed in |
|---|---|---|---|
| Bitnami | helm | >=2.0.0, <2.16.11>=3.0.0, <3.3.2 | 2.16.113.3.2 |
| Go | helm.sh/helm | <2.16.11 | 2.16.11 |
| Go | helm.sh/helm/v3 | >=3.0.0, <3.3.2 | 3.3.2 |
Open a package to see all its vulnerabilities.
Operating systems
No Linux distribution reports this ID.
References
- access.redhat.com https://access.redhat.com/security/cve/CVE-2020-15184
- github.com https://github.com/helm/helm
- github.com https://github.com/helm/helm/commit/6aab63765f99050b115f0aec3d6350c85e8da946
- github.com https://github.com/helm/helm/commit/e7c281564d8306e1dcf8023d97f972449ad74850
- github.com https://github.com/helm/helm/security/advisories/GHSA-9vp5-m38w-j776
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2020-15184
- www.cve.org https://www.cve.org/CVERecord?id=CVE-2020-15184
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.