GitOps Run allows for Kubernetes workload injection
Key facts
- Attack vector
- Adjacent network
- Privileges required
- None
- User interaction
- Required
- Attack complexity
- Low
- Impact type
- Security bypass, Information disclosure
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-284 and CWE-552.
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 [[email protected]](mailto:[email protected])
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| weaveworks | weave-gitops | up to 0.11.0 | — | No fix listed | CNA |
| — | github.com/weaveworks/weave-gitops (Go) | before 0.12.0 | 0.12.0 | Patch available | GHSA-wr3c-g326-486c |
- weave-gitops Vendorweaveworks Affected up to 0.11.0 Fixed in — No fix listed CNA
- github.com/weaveworks/weave-gitops (Go) Vendor— Affected before 0.12.0 Fixed in 0.12.0 Patch available GHSA-wr3c-g326-486c
Remediation
- Fix · GHSA-wr3c-g326-486c github.com/weaveworks/weave-gitops (Go) Fixed in 0.12.0 Advisory →
Timeline
- 2026-10-02 Threatist record created from CVE-2022-23508
- 2026-10-03 Alias added: GHSA-wr3c-g326-486c
References
Patch 2
Advisory 2
More weaveworks vulnerabilities
- TI-2022-16400 Improper object validation allows for arbitrary code execution in GitOps Tools Extension for VSCode CVSS 3.1CRITICAL 9.8
- TI-2022-16401 Improper KubeConfig handling allows arbitrary code execution CVSS 3.1CRITICAL 9.8
- TI-2022-13142 Weave GitOps leaked cluster credentials into logs on connection errors CVSS 3.1CRITICAL 9.0
- TI-2023-17072 Information Disclosure Vulnerability in Weave GitOps Terraform Controller CVSS 3.1HIGH 8.5
- TI-2020-16099 Weave Net Pods running in host PID namespace can be used to escalate other Kubernetes vulnerabilities CVSS 3.1HIGH 8.0
- TI-2022-07568 Weave Gitops Run vulnerable to insecure communication CVSS 3.1HIGH 7.4
Sources
- CVE-2022-23508 · CVE Program
- CVE-2022-23508 · NVD
- FIRST EPSS
- GHSA-wr3c-g326-486c · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences