CVE-2022-23508 GitOps Run allows for Kubernetes workload injection

High 8.9 Published Updated

Local attackers can inject malicious Kubernetes workloads via an unprotected local S3 bucket, leading to unauthorized cluster deployment.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Local or same network only
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2022-23508?

CVE-2022-23508 is a high-severity missing authorization vulnerability in weaveworks weave-gitops, published on 9 Jan 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

Official description

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])

Weakness: CWE-552, CWE-538, CWE-284

Which versions are affected by CVE-2022-23508?

3 open source packages ship an affected version, including github.com/weaveworks/weave-gitops. It affects 1 product.

PackageAffectedFixed in
github.com/weaveworks/weave-gitops GoAll versions0.12.0
github.com/weaveworks/weave-gitops GoAll versions0.12.0
github.com/weaveworks/weave-gitops GoAll versions0.12.0

Products include Weave Weave Gitops.

How do I fix CVE-2022-23508?

Upgrade github.com/weaveworks/weave-gitops to 0.12.0 or later.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2022-23508 being exploited?

There is no known exploitation of CVE-2022-23508 in the wild and no public exploit code.

Sources

Also known as GHSA-wr3c-g326-486c, GO-2023-1377.

Is CVE-2022-23508 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free