Skip to content

vitess allows users to create keyspaces that can deny access to already existing keyspaces

Moderate severity GitHub Reviewed Published Apr 11, 2023 in vitessio/vitess • Updated May 20, 2024

Package

gomod vitess.io/vitess (Go)

Affected versions

< 0.16.1

Patched versions

0.16.1

Description

Impact

Users can either intentionally or inadvertently create a keyspace containing / characters such that from that point on, anyone who tries to view keyspaces from VTAdmin will receive an error. Trying to list all the keyspaces using vtctldclient GetKeyspaces will also return an error.
Note that all other keyspaces can still be administered using the CLI (vtctldclient).

Patches

v16.0.1 (corresponding to 0.16.1 on pkg.go.dev)

Workarounds

Delete the offending keyspace using a CLI client (vtctldclient)

vtctldclient --server ... DeleteKeyspace a/b

Found during a security audit sponsored by the CNCF and facilitated by OSTIF.

References

@deepthi deepthi published to vitessio/vitess Apr 11, 2023
Published to the GitHub Advisory Database Apr 11, 2023
Reviewed Apr 11, 2023
Published by the National Vulnerability Database Apr 14, 2023
Last updated May 20, 2024

Severity

Moderate

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
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
None
Availability
Low

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:N/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:L

EPSS score

0.097%
(42nd percentile)

Weaknesses

CVE ID

CVE-2023-29194

GHSA ID

GHSA-735r-hv67-g38f

Source code

Credits

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