CVE-2020-7919 — helm
HIGHCVE-2020-7919 is a high-severity (CVSS 7.5) CWE-295 vulnerability in github.com/helm/helm. A fix is available for github.com/helm/helm — see the affected versions and patch details below.
Helm uses crypto package vulnerable to panic from malformed X.509 certificate
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2020-7919 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
github.com/helm/helm🐹helm.sh/helm/v3🐹golang.org/x/cryptoReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
The Helm core maintainers have identified a high severity security vulnerability in Go's crypto package affecting all versions prior to Helm 2.16.8 and Helm 3.1.0.
Thanks to @ravin9249 for identifying the vulnerability.
Impact
Go before 1.12.16 and 1.13.x before 1.13.7 (and the crypto/cryptobyte package before 0.0.0-20200124225646-8b5121be2f68 for Go) allows attacks on clients resulting in a panic via a malformed X.509 certificate. This may allow a remote attacker to cause a denial of service.
Patches
A patch to compile Helm against Go 1.14.4 has been provided for Helm 2 and is available in Helm 2.16.8. Helm 3.1.0 and newer are compiled against Go 1.13.7+.
Workarounds
No workaround is available. Users are urged to upgrade.
References
For more information
If you have any questions or comments about this advisory:
- Open an issue in the Helm repository
- For security-specific issues, email us at [email protected]
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/helm/helm | ≥ 2.0.0&&< 2.16.8 | 2.16.8go get github.com/helm/helm@v2.16.8 |
| 🐹Go | helm.sh/helm/v3 | ≥ 3.0.0&&< 3.1.0 | 3.1.0go get helm.sh/helm/v3@v3.1.0 |
| 🐹Go | golang.org/x/crypto | all versions | 0.0.0-20200124225646-8b5121be2f68go get golang.org/x/crypto@v0.0.0-20200124225646-8b5121be2f68 |
Affected Products
debian linuxdebianfedorafedoraprojectgogolangcloud insights telegrafnetappDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/helm/helm, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/helm/helm to 2.16.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-7919 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is CVE-2020-7919 in your dependencies?
Find it across Go, including transitive dependencies.