// For flags

CVE-2020-11013

lookup Function Information Discolosure in Helm

Severity Score

5.0
*CVSS v3.1

Exploit Likelihood

*EPSS

Affected Versions

*CPE

Public Exploits

1
*Multiple Sources

Exploited in Wild

-
*KEV

Decision

-
*SSVC
Descriptions

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'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

Hay una vulnerabilidad de divulgación de información en Helm desde la versión 3.1.0 y versiones anteriores a la versión 3.2.0. "lookup" es una función de plantilla de Helm introducida en Helm versión v3. Puede buscar recursos en el clúster para comprobar la existencia de recursos específicos y obtener detalles sobre ellos. Esto puede ser usado como parte del proceso para renderizar plantillas. El comportamiento documentado de "helm template" afirma que no se adjunta a un clúster remoto. Sin embargo, la función de plantilla "lookup" agregada recientemente evita esta restricción y se conecta al clúster aún durante "helm template" y "helm install|update|delete|rollback --dry-run". El usuario no es notificado de este comportamiento. Al ejecutar "helm template" no debería hacer llamadas a un clúster. Esto es diferente de "install", que se supone que tiene acceso a un clúster para cargar recursos en Kubernetes. Helm versión 2 no está afectado por esta vulnerabilidad. Un autor de gráfico malicioso podría inyectar una "lookup" en un gráfico que, cuando es renderizado por medio de "helm template", realiza búsquedas no anunciadas contra el clúster al que apunta un archivo "KUBECONFIG" de user's. Esta información puede ser revelada por medio de la salida de "helm template". Este problema se ha corregido en Helm 3.2.0

*Credits: N/A
CVSS Scores
Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
None
Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None
Attack Vector
Network
Attack Complexity
Low
Authentication
Single
Confidentiality
Partial
Integrity
None
Availability
None
* Common Vulnerability Scoring System
SSVC
  • Decision:-
Exploitation
-
Automatable
-
Tech. Impact
-
* Organization's Worst-case Scenario
Timeline
  • 2020-03-30 CVE Reserved
  • 2020-04-24 CVE Published
  • 2024-08-04 CVE Updated
  • 2024-08-04 First Exploit
  • 2024-12-17 EPSS Updated
  • ---------- Exploited in Wild
  • ---------- KEV Due Date
CWE
  • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
CAPEC
Affected Vendors, Products, and Versions
Vendor Product Version Other Status
Vendor Product Version Other Status <-- --> Vendor Product Version Other Status
Helm
Search vendor "Helm"
 Helm
Search vendor "Helm" for product "Helm"
 >= 3.1.0 < 3.2.0
Search vendor "Helm" for product "Helm" and version " >= 3.1.0 < 3.2.0"
-
Affected