For your digest
github.com/vitessio/vitess, vitess.io/vitess: Vitess vulnerable to infinite memory consumption and vtgate crash
It touches something Phylax follows. No evidence of use yet.
Does it affect what I run?
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- github.com/vitessio/vitess (Go): from 19.0.0, before 19.0.4
- github.com/vitessio/vitess (Go): from 18.0.0, before 18.0.5
- github.com/vitessio/vitess (Go): every version, before 17.0.7
- vitess.io/vitess (Go): every version, before 0.17.7
- vitess.io/vitess (Go): from 0.18.0, before 0.18.5
- vitess.io/vitess (Go): from 0.19.0, before 0.19.4
- vitess.io/vitess (Go): every version, before 0.17.7; from 0.18.0, before 0.18.5; from 0.19.0, before 0.19.4
The fix
github.com/vitessio/vitess (Go) fixed in 19.0.4
gogo get github.com/vitessio/vitess@v19.0.4Check what is installedgo list -m github.com/vitessio/vitessPaste into Cursor, Lovable or Claude CodeUpgrade the Go dependency github.com/vitessio/vitess to 19.0.4 or the nearest later release, to fix CVE-2024-32886. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.github.com/vitessio/vitess (Go) fixed in 18.0.5
gogo get github.com/vitessio/vitess@v18.0.5Check what is installedgo list -m github.com/vitessio/vitessPaste into Cursor, Lovable or Claude CodeUpgrade the Go dependency github.com/vitessio/vitess to 18.0.5 or the nearest later release, to fix CVE-2024-32886. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.github.com/vitessio/vitess (Go) fixed in 17.0.7
gogo get github.com/vitessio/vitess@v17.0.7Check what is installedgo list -m github.com/vitessio/vitessPaste into Cursor, Lovable or Claude CodeUpgrade the Go dependency github.com/vitessio/vitess to 17.0.7 or the nearest later release, to fix CVE-2024-32886. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.vitess.io/vitess (Go) fixed in 0.17.7
gogo get vitess.io/vitess@v0.17.7Check what is installedgo list -m vitess.io/vitessPaste into Cursor, Lovable or Claude CodeUpgrade the Go dependency vitess.io/vitess to 0.17.7 or the nearest later release, to fix CVE-2024-32886. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.vitess.io/vitess (Go) fixed in 0.18.5
gogo get vitess.io/vitess@v0.18.5Check what is installedgo list -m vitess.io/vitessPaste into Cursor, Lovable or Claude CodeUpgrade the Go dependency vitess.io/vitess to 0.18.5 or the nearest later release, to fix CVE-2024-32886. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.vitess.io/vitess (Go) fixed in 0.19.4
gogo get vitess.io/vitess@v0.19.4Check what is installedgo list -m vitess.io/vitessPaste into Cursor, Lovable or Claude CodeUpgrade the Go dependency vitess.io/vitess to 0.19.4 or the nearest later release, to fix CVE-2024-32886. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
No evidence that it is being used, or can be. It is listed because of what it affects.
Timeline
- First published here, as "For your digest".