ghsa-q8q8-93cv-v6h8
Vulnerability from github
The Helm core maintainers have identified an information disclosure vulnerability in Helm 3.0.0-3.1.2.
Impact
lookup is a Helm template function introduced in Helm v3. It is able to lookup resources in the cluster to check for the existence of specific resources and get details about them. This can be used as part of the process to render templates.
The documented behavior of helm template states that it does not attach to a remote cluster. However, as the recently added lookup template function circumvents this restriction and connects to the cluster even during helm template and helm install|update|delete|rollback --dry-run. The user is not notified of this behavior.
Running helm template should not make calls to a cluster. This is different from install, which is presumed to have access to a cluster in order to load resources into Kubernetes. Helm 2 is unaffected by this vulnerability.
A malicious chart author could inject a lookup into a chart that, when rendered through helm template, performs unannounced lookups against the cluster a user's KUBECONFIG file points to. This information can then be disclosed via the output of helm template.
Patches
This issue has been fixed in Helm 3.2.0
Workarounds
Due to another bug (also fixed in Helm 3.2.0), the command helm lint will fail with an error if the lookup function is used in a chart. Therefore, run helm lint on an untrusted chart before running helm template.
Alternately, setting the KUBECONFIG environment variable to point to an empty Kubernetes configuration file will prevent unintended network connections.
Finally, a chart may be manually analyzed for the presence of a lookup function in any file in the templates/ directory.
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 cncf-helm-security@lists.cncf.io
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "helm.sh/helm/v3"
},
"ranges": [
{
"events": [
{
"introduced": "3.0.0"
},
{
"fixed": "3.1.3"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2020-11013"
],
"database_specific": {
"cwe_ids": [
"CWE-200"
],
"github_reviewed": true,
"github_reviewed_at": "2021-05-24T21:15:16Z",
"nvd_published_at": null,
"severity": "HIGH"
},
"details": "The Helm core maintainers have identified an information disclosure vulnerability in Helm 3.0.0-3.1.2. \n\n### Impact\n\n`lookup` is a Helm template function introduced in Helm v3. It is able to lookup resources in the cluster to check for the existence of specific resources and get details about them. This can be used as part of the process to render templates.\n\nThe documented behavior of `helm template` states that it does not attach to a remote cluster. However, as the recently added `lookup` template function circumvents this restriction and connects to the cluster even during `helm template` and `helm install|update|delete|rollback --dry-run`. The user is not notified of this behavior.\n\nRunning `helm template` should not make calls to a cluster. This is different from `install`, which is presumed to have access to a cluster in order to load resources into Kubernetes. Helm 2 is unaffected by this vulnerability.\n\nA malicious chart author could inject a `lookup` into a chart that, when rendered through `helm template`, performs unannounced lookups against the cluster a user\u0027s `KUBECONFIG` file points to. This information can then be disclosed via the output of `helm template`.\n\n### Patches\n\nThis issue has been fixed in Helm 3.2.0\n\n### Workarounds\n\nDue to another bug (also fixed in Helm 3.2.0), the command `helm lint` will fail with an error if the `lookup` function is used in a chart. Therefore, run `helm lint` on an untrusted chart before running `helm template`.\n\nAlternately, setting the `KUBECONFIG` environment variable to point to an empty Kubernetes configuration file will prevent unintended network connections.\n\nFinally, a chart may be manually analyzed for the presence of a `lookup` function in any file in the `templates/` directory. \n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [the Helm repository](https://github.com/helm/helm/issues)\n* For security-specific issues, email us at [cncf-helm-security@lists.cncf.io](mailto:cncf-helm-security@lists.cncf.io)",
"id": "GHSA-q8q8-93cv-v6h8",
"modified": "2021-05-24T21:15:16Z",
"published": "2021-05-27T18:44:56Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/helm/helm/security/advisories/GHSA-q8q8-93cv-v6h8"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-11013"
},
{
"type": "WEB",
"url": "https://github.com/helm/helm/pull/7969"
},
{
"type": "WEB",
"url": "https://github.com/helm/helm/pull/7969/commits/c67b644a791a8fa61c760a3a0474533e63e74008"
},
{
"type": "WEB",
"url": "https://github.com/helm/helm/releases/tag/v3.2.0"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N",
"type": "CVSS_V3"
}
],
"summary": "Lookup function information discolosure in helm"
}
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.