One Article Review
| Source |  CVE Liste |
|---|---|
| Identifiant | 8299266 |
| Date de publication | 2023-01-09 13:15:10 (vue: 2023-01-09 16:08:11) |
| Titre | CVE-2022-23508 |
| Texte | 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) |
| Envoyé | Oui |
| Condensat | ### 08/12/2022 2022 23508 75268c4 966823b about access advisory: against allow allowing alter any applications applied are attacker been block bucket choosing cloud cluster com/weaveworks/weave comments commits content controls could credentials cve deployment developer disclosed either email endpoint engineer expertise files fixed gitops gomes had has have https://github information inject issue its known kubernetes later leveraging local machine mailto:support@weave more native need needing nor open paulo people pick platform please process processes provide questions references released repository resources resulted run same security see senior should simple software source successful support@weave synchronizing target therefore unauthorized upgrade user users uses version vulnerability want weave weaveworks which who without workaround workarounds workload works |
| Tags | Vulnerability |
| Stories | Uber |
| Notes | |
| Move | 
|
L'article ne semble pas avoir été repris aprés sa publication.
L'article ne semble pas avoir été repris sur un précédent.