CVE-2022-23508
Published: 09 January 2023
Summary
CVE-2022-23508 is a high-severity Improper Access Control (CWE-284) vulnerability in Weave Weave Gitops. Its CVSS base score is 8.8 (High).
Operationally, ranked at the 16.6th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-0577
Vulnerability details
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…
more
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)
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Designating authorized individuals and mandating pre/post-publication reviews enforces access controls on who can publish content publicly.
Security categorization determines the impact level that drives selection of appropriate access-control baselines.
OPSEC measures enforce access restrictions on sensitive supply-chain data and processes.
Identifying users with access to specific system components supports enforcement of proper access controls on information.
Mapping data actions reveals potential improper access controls by showing who can perform actions on data.
Protecting CIA of backups requires access controls to prevent unauthorized access, modification, or deletion.
Approving and monitoring all maintenance activities prevents improper access control by restricting unauthorized personnel from performing maintenance on system components.
Policy and procedures establish documented access controls and responsibilities for media, reducing improper access.