CVE-2022-23508

Weave GitOps is a simple open source developer platform for people who want cloud native applications, without needing Kubernetes expertise. A vulnerability in GitOps run could allow a local user or process to alter a Kubernetes cluster's resources. GitOps run has a local S3 bucket which it uses for synchronizing files that are later applied against a Kubernetes cluster. Its endpoint had no security controls to block unauthorized access, therefore allowing local users (and processes) on the same machine to see and alter the bucket content. By leveraging this vulnerability, an attacker could pick a workload of their choosing and inject it into the S3 bucket, which resulted in the successful deployment in the target cluster, without the need to provide any credentials to either the S3 bucket nor the target Kubernetes cluster. There are no known workarounds for this issue, please upgrade. This vulnerability has been fixed by commits 75268c4 and 966823b. Users should upgrade to Weave GitOps version >= v0.12.0 released on 08/12/2022. ### Workarounds There is no workaround for this vulnerability. ### References Disclosed by Paulo Gomes, Senior Software Engineer, Weaveworks. ### For more information If you have any questions or comments about this advisory: - Open an issue in [Weave GitOps repository](https://github.com/weaveworks/weave-gitops) - Email us at [support@weave.works](mailto:support@weave.works)
Configurations

Configuration 1 (hide)

cpe:2.3:a:weave:weave_gitops:*:*:*:*:*:*:*:*

History

21 Nov 2024, 06:48

Type Values Removed Values Added
CVSS v2 : unknown
v3 : 7.8
v2 : unknown
v3 : 8.8
Summary
  • (es) Weave GitOps es una sencilla plataforma de desarrollo de código abierto para personas que desean aplicaciones nativas de la nube, sin necesidad de experiencia en Kubernetes. Una vulnerabilidad en la ejecución de GitOps podría permitir que un usuario o proceso local altere los recursos de un clúster de Kubernetes. La ejecución de GitOps tiene un depósito S3 local que utiliza para sincronizar archivos que luego se aplican en un clúster de Kubernetes. Su punto final no tenía controles de seguridad para bloquear el acceso no autorizado, lo que permitía a los usuarios (y procesos) locales en la misma máquina ver y alterar el contenido del depósito. Al aprovechar esta vulnerabilidad, un atacante podría elegir una carga de trabajo de su elección e inyectarla en el depósito de S3, lo que resultó en la implementación exitosa en el clúster de destino, sin la necesidad de proporcionar ninguna credencial ni al depósito de S3 ni al clúster de Kubernetes de destino. . No existen soluciones alternativas para este problema; actualice. Esta vulnerabilidad se solucionó mediante las confirmaciones 75268c4 y 966823b. Los usuarios deben actualizar a la versión Weave GitOps >= v0.12.0 lanzada el 12/08/2022. ### Soluciones alternativas No existe ninguna solución alternativa para esta vulnerabilidad. ### Referencias divulgadas por Paulo Gomes, ingeniero de software senior, Weaveworks. ### Para obtener más información Si tiene alguna pregunta o comentario sobre este aviso: - Abra una incidencia en [repositorio Weave GitOps](https://github.com/weaveworks/weave-gitops) - Envíenos un correo electrónico a [support@weave .works](correo a:support@weave.works)
References () https://github.com/weaveworks/weave-gitops/pull/3102/commits/966823bbda8c539a4661e2a4f8607c9307ba6225 - Patch, Third Party Advisory () https://github.com/weaveworks/weave-gitops/pull/3102/commits/966823bbda8c539a4661e2a4f8607c9307ba6225 - Patch, Third Party Advisory
References () https://github.com/weaveworks/weave-gitops/pull/3114/commits/75268c4d2c8f7e4db22c63d76b451ba6545d117f - Patch, Third Party Advisory () https://github.com/weaveworks/weave-gitops/pull/3114/commits/75268c4d2c8f7e4db22c63d76b451ba6545d117f - Patch, Third Party Advisory
References () https://github.com/weaveworks/weave-gitops/security/advisories/GHSA-wr3c-g326-486c - Third Party Advisory () https://github.com/weaveworks/weave-gitops/security/advisories/GHSA-wr3c-g326-486c - Third Party Advisory

07 Nov 2023, 03:44

Type Values Removed Values Added
Summary Weave GitOps is a simple open source developer platform for people who want cloud native applications, without needing Kubernetes expertise. A vulnerability in GitOps run could allow a local user or process to alter a Kubernetes cluster's resources. GitOps run has a local S3 bucket which it uses for synchronizing files that are later applied against a Kubernetes cluster. Its endpoint had no security controls to block unauthorized access, therefore allowing local users (and processes) on the same machine to see and alter the bucket content. By leveraging this vulnerability, an attacker could pick a workload of their choosing and inject it into the S3 bucket, which resulted in the successful deployment in the target cluster, without the need to provide any credentials to either the S3 bucket nor the target Kubernetes cluster. There are no known workarounds for this issue, please upgrade. This vulnerability has been fixed by commits 75268c4 and 966823b. Users should upgrade to Weave GitOps version >= v0.12.0 released on 08/12/2022. ### Workarounds There is no workaround for this vulnerability. ### References Disclosed by Paulo Gomes, Senior Software Engineer, Weaveworks. ### For more information If you have any questions or comments about this advisory: - Open an issue in [Weave GitOps repository](https://github.com/weaveworks/weave-gitops) - Email us at [support@weave.works](mailto:support@weave.works) Weave GitOps is a simple open source developer platform for people who want cloud native applications, without needing Kubernetes expertise. A vulnerability in GitOps run could allow a local user or process to alter a Kubernetes cluster's resources. GitOps run has a local S3 bucket which it uses for synchronizing files that are later applied against a Kubernetes cluster. Its endpoint had no security controls to block unauthorized access, therefore allowing local users (and processes) on the same machine to see and alter the bucket content. By leveraging this vulnerability, an attacker could pick a workload of their choosing and inject it into the S3 bucket, which resulted in the successful deployment in the target cluster, without the need to provide any credentials to either the S3 bucket nor the target Kubernetes cluster. There are no known workarounds for this issue, please upgrade. This vulnerability has been fixed by commits 75268c4 and 966823b. Users should upgrade to Weave GitOps version >= v0.12.0 released on 08/12/2022. ### Workarounds There is no workaround for this vulnerability. ### References Disclosed by Paulo Gomes, Senior Software Engineer, Weaveworks. ### For more information If you have any questions or comments about this advisory: - Open an issue in [Weave GitOps repository](https://github.com/weaveworks/weave-gitops) - Email us at [support@weave.works](mailto:support@weave.works)

Information

Published : 2023-01-09 13:15

Updated : 2024-11-21 06:48


NVD link : CVE-2022-23508

Mitre link : CVE-2022-23508

CVE.ORG link : CVE-2022-23508


JSON object : View

Products Affected

weave

  • weave_gitops
CWE
CWE-284

Improper Access Control

CWE-538

Insertion of Sensitive Information into Externally-Accessible File or Directory

CWE-552

Files or Directories Accessible to External Parties