golang / vulndb

[mirror] The Go Vulnerability Database
Other
555 stars 54 forks source link

x/vulndb: potential Go vuln in github.com/vitessio/vitess: CVE-2023-29195 #1770

Closed GoVulnBot closed 1 year ago

GoVulnBot commented 1 year ago

CVE-2023-29195 references github.com/vitessio/vitess, which may be a Go module.

Description: Vitess is a database clustering system for horizontal scaling of MySQL through generalized sharding. Prior to version 16.0.2, 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. Version 16.0.2, corresponding to version 0.16.2 of the go module, contains a patch for this issue. Some workarounds are available. Always use vtctldclient to create shards, instead of using VTAdmin; disable creating shards from VTAdmin using RBAC; and/or delete the topology record for the offending shard using the client for your topology server.

References:

Cross references: No existing reports found with this module or alias.

See doc/triage.md for instructions on how to triage this report.

modules:
  - module: github.com/vitessio/vitess
    packages:
      - package: vitess
description: |
    Vitess is a database clustering system for horizontal scaling of MySQL through generalized sharding. Prior to version 16.0.2, 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. Version 16.0.2, corresponding to version 0.16.2 of the `go` module, contains a patch for this issue. Some workarounds are available. Always use `vtctldclient` to create shards, instead of using VTAdmin; disable creating shards from VTAdmin using RBAC; and/or delete the topology record for the offending shard using the client for your topology server.
cves:
  - CVE-2023-29195
references:
  - advisory: https://github.com/vitessio/vitess/security/advisories/GHSA-pqj7-jx24-wj7w
  - report: https://github.com/vitessio/vitess/issues/12842
  - fix: https://github.com/vitessio/vitess/pull/12843
  - fix: https://github.com/vitessio/vitess/commit/9dcbd7de3180f47e94f54989fb5c66daea00c920
  - web: https://github.com/vitessio/vitess/releases/tag/v16.0.2
  - web: https://pkg.go.dev/vitess.io/vitess@v0.16.2
jba commented 1 year ago

Duplicate of #1769