Mysql log file obfuscation http://secunia.com/advisories/19034 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 6 Quit 060227 11:16:24 7 Connect root@localhost on test 7 Query /* 7 Quit 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 RHEL3 This issue also affects RHEL2.1
Created attachment 125344 [details] 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.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2006-0544.html