CVE-2023-29195 – vitess.io/vitess

Package

Manager: go
Name: vitess.io/vitess
Vulnerable Version: >=0 <0.16.2

Severity

Level: Medium

CVSS v3.1: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:L

CVSS v4.0: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L

EPSS: 0.00104 pctl0.29006

Details

VTAdmin users that can create shards can deny access to other functions ### Impact Users can either intentionally or inadvertently create a shard containing `/` characters from VTAdmin such that from that point on, anyone who tries to create a new shard from VTAdmin will receive an error. Attempting to view the keyspace(s) will also no longer work. Creating a shard using `vtctldclient` does not have the same problem because the CLI validates the input correctly. ### Patches v16.0.2, corresponding to [0.16.2 on pkg.go.dev](https://pkg.go.dev/vitess.io/vitess@v0.16.2) ### Workarounds - Always use `vtctldclient` to create shards, instead of using VTAdmin - Disable creating shards from VTAdmin using RBAC - Delete the topology record for the offending shard using the client for your topology server. For example, if you created a shard called `a/b` in keyspace `commerce`, and you are running etcd, it can be deleted by doing something like ``` % etcdctl --endpoints "http://${ETCD_SERVER}" del /vitess/global/keyspaces/commerce/shards/a/b/Shard ``` ### References https://github.com/vitessio/vitess/issues/12842 Found during a security audit sponsored by the [CNCF](https://cncf.io) and facilitated by [OSTIF](https://ostif.org).

Metadata

Created: 2023-05-11T19:40:49Z
Modified: 2023-05-11T19:40:49Z
Source: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2023/05/GHSA-pqj7-jx24-wj7w/GHSA-pqj7-jx24-wj7w.json
CWE IDs: ["CWE-20", "CWE-703"]
Alternative ID: GHSA-pqj7-jx24-wj7w
Finding: F184
Auto approve: 1