#46011 [Com]: mysql_real_escape_string is no protection for numeric fields

ID: 46011 Comment by: olafvdspek at gmail dot com Reported By: pablo dot angulo at uam dot es Status: Open Bug Type: Documentation problem Operating System: Irrelevant PHP Version: Irrelevant New Comment: http://php.net/manual/en/function.mysql-query.php should really contain a warning about SQL injection. Even better, mysql_query should be deprecated and replaced by a safe(r) variant. Previous Comments: ------------------------------------------------------------------------ [2008-09-06 17:34:26] pablo dot angulo at uam dot es Description: ------------ mysql_real_escape_string documentation gives the false impression that its use alone will prevent mysql attacks and unauthorized access to the database in all circumstances. For numeric columns, mysql_real_escape_string is not enough. example: $user=mysql_real_escape_string($_GET['user']); $pass=mysql_real_escape_string($_GET['pass']); $id=mysql_real_escape_string($_GET['id']); $query="SELECT x FROM t WHERE user='$user' AND pass='$pass' id=$id"; mysql_query("query); is susceptible to the attack http:example.com/index.php?id=1 OR 1=1 because mysql_real_escape_string does not escape whitespace. The check is_numeric($id) is a solution to the above, putting the number between quotes in the query also is, and using sprintf is another solution, but the documentation does not suggest any of those should be used. There should be at least a pointer to: http://php.net/manual/en/security.database.sql-injection.php so that we newbies know this is not a trivial issue. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=46011&edit=1