CVE-2024-32886: Vitess vulnerable to infinite memory consumption and vtgate crash
Summary When executing the following simple query, the vtgate will go into an endless loop that also keeps consuming memory and eventually will OOM. Details When running the following query, the evalengine will try evaluate it and runs forever. The source of the bug lies in the collation logic that we have. The bug applies to all utf16, utf32 and ucs2 encodings.
Published May 8, 2024 · Updated May 10, 2024
Affected packages
github.com/vitessio/vitess
- Ecosystem
- Go
- Affected
- >= 19.0.0, < 19.0.4
- Fixed in
- 19.0.4
- Check
go list -m github.com/vitessio/vitess
github.com/vitessio/vitess
- Ecosystem
- Go
- Affected
- >= 18.0.0, < 18.0.5
- Fixed in
- 18.0.5
- Check
go list -m github.com/vitessio/vitess
github.com/vitessio/vitess
- Ecosystem
- Go
- Affected
- < 17.0.7
- Fixed in
- 17.0.7
- Check
go list -m github.com/vitessio/vitess
vitess.io/vitess
- Ecosystem
- Go
- Affected
- < 0.17.7
- Fixed in
- 0.17.7
- Check
go list -m vitess.io/vitess
vitess.io/vitess
- Ecosystem
- Go
- Affected
- >= 0.18.0, < 0.18.5
- Fixed in
- 0.18.5
- Check
go list -m vitess.io/vitess
vitess.io/vitess
- Ecosystem
- Go
- Affected
- >= 0.19.0, < 0.19.4
- Fixed in
- 0.19.4
- Check
go list -m vitess.io/vitess
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
When executing the following simple query, the vtgate will go into an endless loop that also keeps consuming memory and eventually will OOM.
Details
When running the following query, the evalengine will try evaluate it and runs forever.
select _utf16 0xFFThe source of the bug lies in the collation logic that we have. The bug applies to all utf16, utf32 and ucs2 encodings. In general, the bug is there for any encoding where the minimal byte length for a single character is more than 1 byte.
The decoding functions for these collations all implement logic like the following to enforce the minimal character length:
https://github.com/vitessio/vitess/blob/8f6cfaaa643a08dc111395a75a2d250ee746cfa8/go/mysql/collations/charset/unicode/utf16.go#L69-L71
The problem is that all the callers of DecodeRune expect progress by returning the number of bytes consumed. This means that if there's only 1 byte left in an input, it will here return still 0 and the caller(s) don't consume the character.
One example of such a caller is the following:
https://github.com/vitessio/vitess/blob/8f6cfaaa643a08dc111395a75a2d250ee746cfa8/go/mysql/collations/charset/convert.go#L73-L79
The logic here moves forward the pointer in the input []byte but if DecodeRune returns 0 in case of error, it will keep running forever. The OOM happens since it keeps adding the ? as the invalid character to the destination buffer infinitely, growing forever until it runs out of memory.
The fix here would be to always return forward progress also on invalid strings.
There's also a separate bug here that even if progress is guaranteed, select _utf16 0xFF will return the wrong result currently. MySQL will pad here the input when the _utf16 introducer is used with leading 0x00 bytes and then decode to UTF-16, resulting in the output of ÿ here.
PoC
select _utf16 0xFFImpact
Denial of service attack by triggering unbounded memory usage.
Credited to dbussink, mattrobenolt, vmg.
References
- https://github.com/vitessio/vitess/security/advisories/GHSA-649x-hxfx-57j2
- https://github.com/vitessio/vitess/commit/2fd5ba1dbf6e9b32fdfdaf869d130066b1b5c0df
- https://github.com/vitessio/vitess/commit/9df4b66550e46b5d7079e21ed0e1b0f49f92b055
- https://github.com/vitessio/vitess/commit/c46dc5b6a4329a10589ca928392218d96031ac8d
- https://github.com/vitessio/vitess/commit/d438adf7e34a6cf00fe441db80842ec669a99202
- https://github.com/vitessio/vitess/blob/8f6cfaaa643a08dc111395a75a2d250ee746cfa8/go/mysql/collations/charset/convert.go#L73-L79
- https://github.com/vitessio/vitess/blob/8f6cfaaa643a08dc111395a75a2d250ee746cfa8/go/mysql/collations/charset/unicode/utf16.go#L69-L71
- https://nvd.nist.gov/vuln/detail/CVE-2024-32886
- https://github.com/advisories/GHSA-649x-hxfx-57j2
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-104252
Vitess vttablet /twopcz reflected XSS
critical9.8Oct 15, 2026CVE-2026-65959
Vitess: Missing authorization on vttablet /debug/vrlog exposes live VReplication SQL data
medium5.3No fixAug 18, 2026CVE-2026-27969
Vitess users with backup storage access can write to arbitrary file paths on restore
critical9.3Feb 27, 2026CVE-2026-27965
Vitess users with backup storage access can gain unauthorized access to production deployment environments
high8.4No fixFeb 26, 2026CVE-2024-53257
Vitess allows HTML injection in /debug/querylogz & /debug/env
medium4.9Dec 3, 2024
