{"answers":{"affected":"3 open source packages ship an affected version, including helm.sh/helm/v3 and helm. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-11013 in the wild and no public exploit code.","fix":"Upgrade helm.sh/helm/v3 to 3.1.3 or later.","what":"CVE-2020-11013 is a high-severity vulnerability in Helm, published on 24 Apr 2020. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-11013 and fix it if it is affected.\n\nWhat it is: CVE-2020-11013 is a high-severity vulnerability in Helm, published on 24 Apr 2020. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-11013 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- helm.sh/helm/v3 (Go): affected from 3.0.0; fixed in 3.1.3\n- helm.sh/helm/v3 (Go): affected from 3.0.0; fixed in 3.1.3\n- helm (Bitnami): affected from 3.1.0; fixed in 3.2.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2020-11013/ (Markdown: https://insights.sbomify.com/CVE-2020-11013/index.md)","id":"CVE-2020-11013","markdown":"https://insights.sbomify.com/CVE-2020-11013/index.md","name":"CVE-2020-11013","record":{"aliases":["BIT-helm-2020-11013","GHSA-q8q8-93cv-v6h8","UBUNTU-CVE-2020-11013"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Kubernetes package manager","requires_auth":"low_privilege","summary":"A malicious Helm chart can leak cluster information via the lookup function during template rendering, bypassing the expected offline behavior.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"helm","vendor":"helm"}],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Their is an information disclosure vulnerability in Helm from version 3.1.0 and before version 3.2.0. `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, a 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\u0026#39;s `KUBECONFIG` file points to. This information can then be disclosed via the output of `helm template`. This issue has been fixed in Helm 3.2.0","ecosystems":["Bitnami","Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"lookup Function Information Discolosure in Helm","id":"CVE-2020-11013","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":3,"n_references":2,"next":{"headline":"BIP LI01 output reordering may cause malformed SLP MINT transactions in Electron-Cash-SLP","id":"CVE-2020-11014"},"packages":[{"ecosystem":"Bitnami","fixed":["3.2.0"],"introduced":["3.1.0"],"last_affected":[],"package":"helm","purl":"pkg:bitnami/helm","source":"BIT-helm-2020-11013"},{"ecosystem":"Go","fixed":["3.1.3"],"introduced":["3.0.0"],"last_affected":[],"package":"helm.sh/helm/v3","purl":null,"source":"GHSA-q8q8-93cv-v6h8"},{"ecosystem":"Go","fixed":["3.1.3"],"introduced":["3.0.0"],"last_affected":[],"package":"helm.sh/helm/v3","purl":"pkg:golang/helm.sh/helm/v3","source":"GHSA-q8q8-93cv-v6h8"}],"prev":{"headline":"Authentication bypass MinIO Admin API","id":"CVE-2020-11012"},"products":["Helm"],"published":"2020-04-24","related":[{"cvss_score":9.8,"headline":"Helm Unsafe Link Following","id":"CVE-2019-18658","kev_date_added":null,"published":"2019-11-12"},{"cvss_score":9.8,"headline":"Helm Improper Certificate Validation","id":"CVE-2019-1010275","kev_date_added":null,"published":"2019-07-17"},{"cvss_score":9.1,"headline":"Information disclosure in n/a","id":"CVE-2019-25210","kev_date_added":null,"published":"2024-03-03"},{"cvss_score":8.5,"headline":"Helm Chart Dependency Updating With Malicious Chart.yaml Content And Symlink Can Lead To Code Execution","id":"CVE-2025-53547","kev_date_added":null,"published":"2025-07-08"},{"cvss_score":8.4,"headline":"Helm has a path traversal in plugin metadata version enables arbitrary file write outside Helm plugin directory","id":"CVE-2026-35204","kev_date_added":null,"published":"2026-04-09"},{"cvss_score":8.4,"headline":"Helm's plugin verification fails open when .prov is missing, allowing unsigned plugin install","id":"CVE-2026-35205","kev_date_added":null,"published":"2026-04-09"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["helm"]},"summary":"A malicious Helm chart can leak cluster information via the lookup function during template rendering, bypassing the expected offline behavior.","url":"https://insights.sbomify.com/CVE-2020-11013/"}