Re:Format string vulnerability found in 'sudo'
by gizzlon on Tuesday January 31, 2012 @04:39AM
(#3532527)
Actually, isn't the escaping done serversiden when using placeholders?
At least in Perl, there's no need to escape placeholder values explicitly. I believe the prepared statement is stored on the server, and then the values sent later. Of course the escaping could be the work of the driver.. anyone know?
Re:Format string vulnerability found in 'sudo'
by rjh29 on Tuesday January 31, 2012 @06:19AM
(#3532793)
See "Prepared Statement Support" from http://search.cpan.org/perldoc?DBD::mysql#Class_Methods
Prepared statements are disabled by default and require MySQL >= 4.1.3. Instead, the driver does the placeholder replacement on the client, and prepare() does nothing clever at all.
Re:Format string vulnerability found in 'sudo'
by gizzlon on Tuesday January 31, 2012 @07:08AM
(#3532902)
hm.. could be useful information.. thanks
Re:Format string vulnerability found in 'sudo'
by flomo on Tuesday January 31, 2012 @12:51AM
(#3532052)
Building dynamic SQL strings for comparison can sometimes be handy (e.g. with LIKE), so it's really too bad there's no server-side SQL escape function, at least in the sql dialects I'm familiar with.
http://dev.mysql.com/doc/refman/5.0/en/mysql-real-escape-str...
I'm sure what you meant was a server-side escaping function which is obviously pointless, but I did want to point out that MySQL's client driver does ship with one that you can use so you don't have to write your own.