php addslashes and other methods of clearing spaces are unsafe_PHP Tutorial

The method of clearing spaces is unsafe, partly because there are so many spaces in the characters, for example "The problem with "addslashes" is that a hacker can replace the single quote with 0xbf27, and addslashes just changes 0xbf27 to 0xbf5c27, making it a valid multi-word section characters, 0xbf5c among them will still be regarded as a single quote, so addslashes cannot successfully intercept "

It is best to check whether it is int according to the specific parameter requirements, plus the parameter operation method of the database. .In fact, this is a SQL problem of the database, which should be solved from the source database itself, but some databases provide corresponding methods.

SQL injection attack is the most common method used by hackers to attack websites. If your site does not use strict user input validation, it is often vulnerable to SQL injection attacks. SQL injection attacks are usually implemented by submitting bad data or query statements to the site database, which may cause records in the database to be exposed, changed or deleted.

In order to prevent SQL injection attacks, PHP comes with a function that can process the input string and perform preliminary security processing on the input at the lower level, that is, Magic Quotes. (php.ini magic_quotes_gpc). If the magic_quotes_gpc option is enabled, single quotes, double quotes, and other characters in the input string will be automatically preceded by backslashes.

But Magic Quotes is not a very universal solution, it does not block all potentially dangerous characters, and Magic Quotes is not enabled on many servers. Therefore, we also need to use various other methods to prevent SQL injection.

Many databases provide this input data processing functionality natively. For example, PHP's MySQL operation functions include addslashes(), mysql_real_escape_string(), mysql_escape_string() and other functions, which can escape special characters and characters that may cause database operation errors. So what are the differences between these three functional functions? Let’s talk about it in detail below.

Although many domestic PHP programmers still rely on addslashes to prevent SQL injection, it is recommended that everyone strengthen checks to prevent SQL injection in Chinese. The problem with addslashes is that hackers can use 0xbf27 instead of single quotes, while addslashes only changes 0xbf27 to 0xbf5c27, which becomes a valid multi-byte character. 0xbf5c is still regarded as a single quote, so addslashes cannot successfully intercept.

Of course, addslashes is not useless. It is used for processing single-byte strings. For multi-byte characters, use mysql_real_escape_string.

Another example of get_magic_quotes_gpc in the PHP manual:
if (!get_magic_quotes_gpc()) {
$lastname = addslashes($_POST['lastname']);
} else {
$lastname = $_POST['lastname'];
}
It is best to check $_POST['lastname'] when magic_quotes_gpc is already open.

Let’s talk about the difference between the two functions mysql_real_escape_string and mysql_escape_string:
mysql_real_escape_string can only be used under (PHP 4 >= 4.3.0, PHP 5). Otherwise, you can only use mysql_escape_string. The difference between the two is: mysql_real_escape_string takes into account the current character set of the connection, while mysql_escape_string does not.

To summarize:

* addslashes() is a forced addition;
* mysql_real_escape_string() will determine the character set, but there are requirements for the PHP version;
* mysql_escape_string does not consider the connection the current character set.

To prevent sql injection in dz, you use the addslashes function. At the same time, there are some replacements in the dthmlspecialchars function $string = preg_replace('/&(((#(d{3,5}|x[a -fA-F0-9]{4}));)/', '&\1', this replacement solves the injection problem and also solves some problems with Chinese garbled characters