MySQL Bugs: #45010: invalid memory reads during parsing some strange statements

Bug #45010	invalid memory reads during parsing some strange statements
Submitted:	21 May 2009 16:14	Modified:	14 Sep 2009 19:52
Reporter:	Shane Bester (Platinum Quality Contributor)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Parser	Severity:	S1 (Critical)
Version:	5.0.82, 5.1.34, 5.1.35, 6.0.12	OS:	Linux (32-bit fc8)
Assigned to:	Davi Arnaut	CPU Architecture:	Any
Tags:	DESCRIBE, GIGO, valgrind

File:	Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

On *nix platforms use the split command e.g. split -b 50MB <my_large_archive> <my_split_archive_prefix>
On windows use WinZip or a similar utility to split the large file

testcase to fuzz test the describe sql syntax. see top of file for host, port, user settings

Attachment: bug45010.c (text/x-csrc), 6.35 KiB.

this testcase reveals quite a few valgrind errors in parser. full output attached (best pipe testcase output to a file also).

Attachment: bug45010_5.1.35_complete_valgrind.txt (text/plain), 19.16 KiB.