CVE-2022-23508
GitOps Run allows for Kubernetes workload injection
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
- Email us at [email protected]
Attack profile
How easy it is to exploit
- Attack vector
- Adjacent network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- Required
What an attacker can affect
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Exploit likelihood
What each source reports
CVE List Score used
GitOps Run allows for Kubernetes workload injection
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
- Email us at [email protected]
- Record
CVE-2022-23508- CVSS 3.1
- 8.9 High
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H - Weakness
- CWE-284, CWE-538, CWE-552
- Updated
- 2026-11-02
EUVDEUVD-2023-0577
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
- Email us at [email protected]
- Record
EUVD-2023-0577- CVSS 3.1
- 8.9 High
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-wr3c-g326-486c
GitOps Run allows for Kubernetes workload injection
Impact
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 synchronising files that are later applied against a Kubernetes cluster. Its endpoint had no security controls to block unauthorised 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.
Patches
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
- Email us at [email protected]
- Record
GHSA-wr3c-g326-486c- CVSS 3.1
- 8.8 High
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H - Weakness
- CWE-284, CWE-552
- Updated
- 2026-11-02
NVD
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
- Email us at [email protected]
- Record
CVE-2022-23508- CVSS 3.1
- 8.8 High
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H - CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Weakness
- CWE-284, CWE-538, CWE-552
- Updated
- 2026-11-02
OSV
GitOps Run allows for Kubernetes workload injection
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
- Email us at [email protected]
- Record
CVE-2022-23508- CVSS 3.1
- 8.8 High
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H - Weakness
- CWE-284, CWE-538, CWE-552
- Updated
- 2026-11-02
OSVGHSA-wr3c-g326-486c
GitOps Run allows for Kubernetes workload injection
Impact
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 synchronising files that are later applied against a Kubernetes cluster. Its endpoint had no security controls to block unauthorised 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.
Patches
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
- Email us at [email protected]
- Record
GHSA-wr3c-g326-486c- CVSS 3.1
- 8.8 High
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H - Weakness
- CWE-284, CWE-552
- Updated
- 2026-11-02
OSVGO-2023-1377 No score
GitOps Run allows for Kubernetes workload injection in github.com/weaveworks/weave-gitops
GitOps Run allows for Kubernetes workload injection in github.com/weaveworks/weave-gitops
- Record
GO-2023-1377- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
github.com/weaveworks/weave-gitopsGo |
through 0.11.0 | 0.12.0 |
github.com/weaveworks/weave-gitopsGo |
before 0.12.0 | 0.12.0 |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2022-23508 is a high vulnerability (CVSS 8.9) in Weave Gitops, published January 9, 2023. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.33%, the 26th percentile. Fixed in github.com/weaveworks/weave-gitops 0.12.0.
References
github.com/weaveworks/weave-gitops/security/advisories/GHSA-wr3c-g326-486c
nvd.nist.gov/vuln/detail/CVE-2022-23508