Quantcast
Channel: CodeSection,代码区,网络安全 - CodeSec
Viewing all articles
Browse latest Browse all 12749

Is FILTER_SANITIZE_EMAIL sufficient or is mysql& ...

0
0

I am checking input against a database like this:

$email = $_POST['newsletter_email']; $email = filter_var($email, FILTER_SANITIZE_EMAIL);

and then:

$is_user = $db->count_rows('users', "WHERE email='" . $email . "'");

The question is, is it good enough? Or should I also use mysql_real_escape_string ?

There are two parts to this question.

How to validate an email address. How to prevent SQL Injection . Input Validation $email = filter_var($_POST['email'], FILTER_VALIDATE_EMAIL); if ($email !== false) { // Well, you've got yourself a valid email address! } Preventing SQL Injection

Don't use mysql_real_escape_string() . The proper way to prevent SQL Injection is to use Parameterized Queries. Also known as Prepared Statements.

Recommended reading:

SQL injection that gets around mysql_real_escape_string() https://kraft.im/2015/05/how-emoji-saved-your-sites-hide/

Your code should look like this:

$stmt = $db->prepare('SELECT count(userid) FROM users WHERE email = ?'); if ($stmt->exec([ $email ])) { $is_user = $stmt->fetchColumn(0); }

If that seems too cumbersome for you, you can load up the EasyDB library and make your query look like this:

$is_user = $db->cell('SELECT count(userid) FROM users WHERE email = ?', $email);

Please retire the use of input escaping and adopt prepared statements . They send the query and the parameters in separate packets, which means altering the query structure is not possible, even with Unicode hacks.

Important

You must use prepared statements correctly (i.e. NEVER concatenate user input with the query string passed to prepare() ) to achieve this guaranteed level of security.

Furthermore, in php, some drivers will by default emulate the prepared statements. From the PHP manual :

PDO::ATTR_EMULATE_PREPARES Enables or disables emulation of prepared statements. Some drivers do not support native prepared statements or have limited support for them. Use this setting to force PDO to either always emulate prepared statements (if TRUE ), or to try to use native prepared statements (if FALSE ). It will always fall back to emulating the prepared statement if the driver cannot successfully prepare the current query. Requires bool.

Emulated prepared statements does not offer the same security guarantee (i.e. data/instruction separation ) as true prepared statements. To be safe, disable emulated prepares.

$db = new PDO(/* etc */); $db->setAttribute(PDO::ATTR_EMULATE_PREPARES, false);


Viewing all articles
Browse latest Browse all 12749