{"answers":{"affected":"2 open source packages ship an affected version, including vitess.io/vitess. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-29195 in the wild and no public exploit code.","fix":"Upgrade vitess.io/vitess to 0.16.2 or later.","what":"CVE-2023-29195 is a medium-severity denial of service vulnerability in vitessio vitess, published on 11 May 2023. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-29195 and fix it if it is affected.\n\nWhat it is: CVE-2023-29195 is a medium-severity denial of service vulnerability in vitessio vitess, published on 11 May 2023. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-29195 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- vitess.io/vitess (Go): affected all versions; fixed in 0.16.2\n- vitess.io/vitess (Go): affected all versions; fixed in 0.16.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-29195/ (Markdown: https://insights.sbomify.com/CVE-2023-29195/index.md)","id":"CVE-2023-29195","markdown":"https://insights.sbomify.com/CVE-2023-29195/index.md","name":"CVE-2023-29195","record":{"aliases":["AZL-26696","GHSA-pqj7-jx24-wj7w"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Vitess database clustering","requires_auth":"high_privilege","summary":"Users with shard creation privileges can cause denial of service in VTAdmin by creating shards with invalid characters, blocking further shard creation and keyspace viewing.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"vitess","vendor":"linuxfoundation"}],"cvss":{"score":4.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-703","name":"Improper Check or Handling of Exceptional Conditions"},{"id":"CWE-20","name":"Improper Input Validation"}],"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.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Vitess VTAdmin users that can create shards can deny access to other functions","id":"CVE-2023-29195","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"denial_of_service","year":"2023"},"n_packages":2,"n_references":6,"next":{"headline":"HTML injection via topic embedding in Discourse","id":"CVE-2023-29196"},"packages":[{"ecosystem":"Go","fixed":["0.16.2"],"introduced":["0"],"last_affected":[],"package":"vitess.io/vitess","purl":null,"source":"GHSA-pqj7-jx24-wj7w"},{"ecosystem":"Go","fixed":["0.16.2"],"introduced":["0"],"last_affected":[],"package":"vitess.io/vitess","purl":"pkg:golang/vitess.io/vitess","source":"GHSA-pqj7-jx24-wj7w"}],"prev":{"headline":"vitess allows users to create keyspaces that can deny access to already existing keyspaces","id":"CVE-2023-29194"},"products":["vitess"],"published":"2023-05-11","related":[{"cvss_score":9.8,"headline":"Vitess vttablet /twopcz reflected XSS","id":"CVE-2026-104252","kev_date_added":null,"published":"2026-10-13"},{"cvss_score":9.3,"headline":"Vitess users with backup storage access can write to arbitrary file paths on restore","id":"CVE-2026-27969","kev_date_added":null,"published":"2026-02-26"},{"cvss_score":8.4,"headline":"Vitess users with backup storage access can gain unauthorized access to production deployment environments","id":"CVE-2026-27965","kev_date_added":null,"published":"2026-02-26"},{"cvss_score":4.1,"headline":"vitess allows users to create keyspaces that can deny access to already existing keyspaces","id":"CVE-2023-29194","kev_date_added":null,"published":"2023-04-14"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-01-24","vendors":["vitessio"]},"summary":"Users with shard creation privileges can cause denial of service in VTAdmin by creating shards with invalid characters, blocking further shard creation and keyspace viewing.","url":"https://insights.sbomify.com/CVE-2023-29195/"}