Skip to content

GHSA-cjjc-xp8v-855w BIT-golang-2020-7919 CVE-2020-7919 GO-2022-0229

Helm uses crypto package vulnerable to panic from malformed X.509 certificate

High Go
Severity
7.5 / 10
High · CVSS 3.1
Exploit chance (EPSS)
2.65%
Chance of exploitation in the next 30 days. Higher than 85.61% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-295 Improper Certificate Validation
Fix
Available
4 packages have a fixed version

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:

Affected versions

Go

PackageVulnerableFixed in
github.com/helm/helm
>= 2.0.0, < 2.16.8
2.16.8
golang.org/x/crypto
< 0.0.0-20200124225646-8b5121be2f68
0.0.0-20200124225646-8b5121be2f68
helm.sh/helm/v3
>= 3.0.0, < 3.1.0
3.1.0
stdlib
< 1.12.16
>= 1.13.0-0, < 1.13.7
1.12.16
1.13.7

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

github.com/helm/helm Go → 2.16.8

go
go get github.com/helm/helm@v2.16.8 && go mod tidy

golang.org/x/crypto Go → 0.0.0-20200124225646-8b5121be2f68

go
go get golang.org/x/crypto@v0.0.0-20200124225646-8b5121be2f68 && go mod tidy

helm.sh/helm/v3 Go → 3.1.0

go
go get helm.sh/helm/v3@v3.1.0 && go mod tidy

stdlib Go → 1.13.7

go
go get stdlib@v1.13.7 && go mod tidy

Severity breakdown

CVSS 3.1 7.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Weakness

CWE-295: Improper Certificate Validation

The product does not validate, or incorrectly validates, a certificate.

How to prevent it
  • Architecture and Design, Implementation: Certificates should be carefully managed and checked to assure that data are encrypted with the intended owner's public key.
  • Implementation: If certificate pinning is being used, ensure that all relevant properties of the certificate are fully validated before the certificate is pinned, including the hostname.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-4374-p667-p6c8
HTTP/2 rapid reset can cause excessive work in net/http
High Known exploited Also affects stdlib
CVE-2020-0601
Certificate validation bypass on Windows in crypto/x509
High Known exploited Also affects stdlib
RUSTSEC-2026-0382
Distrust compromised intermediate certificates in crypto/x509
Medium Also affects stdlib
GO-2026-6613
HTTP/1 server connection desynchronization after 2xx CONNECT response in net/http
High Also affects stdlib
GO-2026-6609
Lack of limit on size of parsed Range headers in net/http
High Also affects stdlib
GO-2026-6608
Memory limit bypass when parsing MIME headers in net/textproto, mime/multipart
High Also affects stdlib
GO-2026-6607
Reject malformed ECH outer extension references in crypto/tls
High Also affects stdlib
GO-2026-6604
Root.Mkdir(All) can follow junctions out of the root on Windows in os
Critical Also affects stdlib

Credits: Project Wycheproof

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor