Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

helm.sh/helm

Go package

Overview

Newest range
2.16.11
Last CVE
17 Sep 2020
Go 6 version ranges 5 affected
2 Critical
0 High
2 Medium
3 Low

Package versions

Version ranges and their known vulnerabilities
VersionsRangeDirect vulnerabilities
2.16.11 and later versions 0000
2.15.2 up to 2.16.11 0013
2.12.2 up to 2.15.2 1013
2.7.2 up to 2.12.2 1023
2.0.0 up to 2.7.2 2023
before 2.0.0 all earlier versions 1003

No known vulnerabilities in 2.16.11 and later versions

Nothing in our data affects this version.

6 ranges in total. Each row is a range of versions with the same vulnerabilities, newest first. The data names only the versions where something changes (first affected, fixed), so the versions in between are a range.

Vulnerabilities · 7

Known vulnerabilities of this package
CVESeverityPublishedVulnerableFixed in
CVE-2020-15187helm: write access to the git repository or plugin archive causing causing a local execution attack MEDIUM 17 Sep 2020 >=2.0.0, <2.16.11 2.16.11
CVE-2020-15186helm: plugin names are not sanitized properly LOW 17 Sep 2020 <2.16.11 2.16.11
CVE-2020-15185helm: write access to the index file allows an attacker to inject bad chart into repository LOW 17 Sep 2020 <2.16.11 2.16.11
CVE-2020-15184helm: Chart.yaml is not properly sanitized lead to injection of unwanted information into chart LOW 17 Sep 2020 <2.16.11 2.16.11
CVE-2019-18658Helm Unsafe Link Following CRITICAL 12 Nov 2019 >=2.0.0, <2.15.2 2.15.2
CVE-2019-1010275Helm Improper Certificate Validation CRITICAL 17 Jul 2019 <2.7.2 2.7.2
CVE-2019-1000008Helm Path Traversal MEDIUM 4 Feb 2019 >=2.0.0, <2.12.2 2.12.2

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.