CVE-2022-23508

GitOps Run allows for Kubernetes workload injection

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]

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.

CVE-2022-23508 has a CVSS score of 8.8 (High). The vector is reachable from an adjacent network, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.12.0); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

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.

1. What is CVE-2022-23508? CVE-2022-23508 is a high-severity security vulnerability in github.com/weaveworks/weave-gitops (go), affecting versions <= 0.11.0. It is fixed in 0.12.0.
2. How severe is CVE-2022-23508? CVE-2022-23508 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/weaveworks/weave-gitops are affected by CVE-2022-23508? github.com/weaveworks/weave-gitops (go) versions <= 0.11.0 is affected.
4. Is there a fix for CVE-2022-23508? Yes. CVE-2022-23508 is fixed in 0.12.0. Upgrade to this version or later.
5. Is CVE-2022-23508 exploitable, and should I be worried? Whether CVE-2022-23508 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-23508 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-23508? Upgrade github.com/weaveworks/weave-gitops to 0.12.0 or later.

Other vulnerabilities in github.com/weaveworks/weave-gitops