Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
8.8
CVE-2022-23508: Weave GitOps can let local users inject workloads
CVE-2022-23508 · published 3 years ago
Summary
Weave GitOps version before v0.12.0 lets anyone on the same machine add or change files that are automatically applied to your Kubernetes cluster. This could let an attacker place their own code into the cluster without any credentials. Upgrade to version v0.12.0 or later to stop this behavior.
What to do
- Update github.com weaveworks to version 0.12.0.
- Update weave weave_gitops to version 0.12.0 or later.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| go | github.com | weaveworks |
<= 0.11.0 Fix: upgrade to 0.12.0
|
| – | weave | weave_gitops |
< 0.12.0 cpe:2.3:a:weave:weave_gitops:*:*:*:*:*:*:*:* |
Original advisory text
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](https://github.com/weaveworks/weave-gitops)
- Email us at [[email protected]](mailto:[email protected])
### 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])
References
- https://github.com/advisories/GHSA-wr3c-g326-486c
- https://github.com/weaveworks/weave-gitops/pull/3102/commits/966823bbda8c539a466... URL
- https://github.com/weaveworks/weave-gitops/pull/3114/commits/75268c4d2c8f7e4db22... URL
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/23xxx/CVE-2022-23508... Vendor Advisory
- https://github.com/weaveworks/weave-gitops/security/advisories/GHSA-wr3c-g326-48... Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2022-23508 Vendor Advisory
Internet-facing
14 days
Internal
At next upgrade
- Not known to be exploited
- Needs hands-on effort to exploit
- Gives an attacker full control
Severity
8.8
High
Type
CWE-284Improper Access Control
CWE-552Files or Directories Accessible to External Parties
CWE-538Insertion of Sensitive Information into Externally-Accessible File or Directory
Timeline
Published9 Jan 2023
Updated4 Nov 2026
First seen6 Mar 2026
Track software like this
Free during beta