Mysql log file obfuscation
The following text is from tgl:
Yeah, problem confirmed locally: the query log message is truncated,
060227 11:15:47 6 Connect root@localhost on test
6 Query /* x */ select 2+2
060227 11:16:24 7 Connect root@localhost on test
7 Query /*
The report is perhaps deliberately obscure: you can *not* exploit this
through mysql_query() because it expects a null-terminated string
anyway. But you can exploit it through mysql_real_query() which takes
a pointer and count.
I'd class the severity as pretty low, since all it allows is hiding
some traces of an attack after the attacker has already broken into
the database. But since MySQL make a point of how mysql_real_query()
supports embedded nulls in the query string, it's certainly a bug.
This issue also affects FC3
attachment 125344 [details] is a testcase from tgl:
I've attached a test case. Start the server with query logging enabled
(easiest way is to modify the init script to add "--log" to the
mysqld_safe command line), run program, look at log file.
This is fixed by upstream changes in 4.1.19.