Skip to content

GitOps Run allows for Kubernetes workload injection

High severity GitHub Reviewed Published Jan 9, 2023 in weaveworks/weave-gitops • Updated Jan 29, 2023

Package

gomod github.com/weaveworks/weave-gitops (Go)

Affected versions

<= 0.11.0

Patched versions

0.12.0

Description

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:

References

@souleb souleb published to weaveworks/weave-gitops Jan 9, 2023
Published by the National Vulnerability Database Jan 9, 2023
Published to the GitHub Advisory Database Jan 9, 2023
Reviewed Jan 9, 2023
Last updated Jan 29, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Adjacent
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

EPSS score

0.042%
(5th percentile)

Weaknesses

CVE ID

CVE-2022-23508

GHSA ID

GHSA-wr3c-g326-486c

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.