# CVE-2024-32886: Vitess vulnerable to infinite memory consumption and vtgate crash > Attackers can cause vtgate to crash via infinite memory consumption using a specific query, impacting database availability. - **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 8 May 2024 - **Updated:** 2 Aug 2024 - **Also known as:** AZL-40360, AZL-40493, GHSA-649x-hxfx-57j2, GO-2024-2826 ## What is CVE-2024-32886? CVE-2024-32886 is a medium-severity denial of service vulnerability in vitessio vitess, published on 8 May 2024. An attacker needs administrator access to exploit it, with no action from the victim. ### Official description Vitess is a database clustering system for horizontal scaling of MySQL. When executing the following simple query, the `vtgate` will go into an endless loop that also keeps consuming memory and eventually will run out of memory. This vulnerability is fixed in 19.0.4, 18.0.5, and 17.0.7. Weakness: CWE-835 (Loop with Unreachable Exit Condition) ## Which versions are affected by CVE-2024-32886? 13 open source packages ship an affected version, including github.com/vitessio/vitess and vitess.io/vitess. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/vitessio/vitess` | Go | All versions | 17.0.7 | | `github.com/vitessio/vitess` | Go | All versions | 17.0.7 | | `github.com/vitessio/vitess` | Go | From 18.0.0 | 18.0.5 | | `github.com/vitessio/vitess` | Go | From 18.0.0 | 18.0.5 | | `github.com/vitessio/vitess` | Go | From 19.0.0 | 19.0.4 | | `github.com/vitessio/vitess` | Go | From 19.0.0 | 19.0.4 | | `vitess.io/vitess` | Go | All versions | 0.17.7, 0.18.5, 0.19.4 | | `vitess.io/vitess` | Go | All versions | 0.17.7 | | `vitess.io/vitess` | Go | All versions | 0.17.7 | | `vitess.io/vitess` | Go | From 0.18.0 | 0.18.5 | | `vitess.io/vitess` | Go | From 0.18.0 | 0.18.5 | | `vitess.io/vitess` | Go | From 0.19.0 | 0.19.4 | | `vitess.io/vitess` | Go | From 0.19.0 | 0.19.4 | ## How do I fix CVE-2024-32886? Upgrade github.com/vitessio/vitess to a fixed version for your release line: 17.0.7, 18.0.5 or 19.0.4. ## Is CVE-2024-32886 being exploited? There is no known exploitation of CVE-2024-32886 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-32886 and fix it if it is affected. What it is: CVE-2024-32886 is a medium-severity denial of service vulnerability in vitessio vitess, published on 8 May 2024. An attacker needs administrator access to exploit it, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-32886 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/vitessio/vitess (Go): affected all versions; fixed in 17.0.7 - github.com/vitessio/vitess (Go): affected all versions; fixed in 17.0.7 - github.com/vitessio/vitess (Go): affected from 18.0.0; fixed in 18.0.5 - github.com/vitessio/vitess (Go): affected from 18.0.0; fixed in 18.0.5 - github.com/vitessio/vitess (Go): affected from 19.0.0; fixed in 19.0.4 - github.com/vitessio/vitess (Go): affected from 19.0.0; fixed in 19.0.4 - vitess.io/vitess (Go): affected all versions; fixed in 0.17.7, 0.18.5, 0.19.4 - vitess.io/vitess (Go): affected all versions; fixed in 0.17.7 - vitess.io/vitess (Go): affected all versions; fixed in 0.17.7 - vitess.io/vitess (Go): affected from 0.18.0; fixed in 0.18.5 - vitess.io/vitess (Go): affected from 0.18.0; fixed in 0.18.5 - vitess.io/vitess (Go): affected from 0.19.0; fixed in 0.19.4 Task: 1. 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. 2. 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. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-32886/ (Markdown: https://insights.sbomify.com/CVE-2024-32886/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-32886 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-32886 - OSV: https://osv.dev/vulnerability/CVE-2024-32886 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-32886/ Summaries are generated and may contain mistakes; the official description above is the record.