Everyone knows that PHP is already the most popular web application programming language. But like other scripting languages, PHP also has several dangerous security holes. So in this tutorial, we'll take a look at a few practical tips to help you avoid some common PHP security issues.
Usually during the development process, many programmers always forget to make program error reports. This is a huge mistake, because proper error reports are not only the best debugging tools, but also excellent security vulnerability detection tools. , this allows you to find out as much as possible the problems you will encounter before the application is actually launched.
Of course there are many ways to enable error reporting. For example, in the php.in configuration file you can set it to be enabled at runtime
Start error reporting
error_reporting(E_ALL);
Disable error reporting
error_reporting(0);
There are several PHP properties that need to be set to OFF. Generally, they exist in PHP4, but their use is not recommended in PHP5. Especially in PHP6, these attributes were removed.
Register global variables
When register_globals is set to ON, it is equivalent to setting Environment, GET, POST, COOKIE or Server variables are defined as global variables. At this time, you don't need to write $_POST['username'] to get the form variable 'username'. You only need '$username' to get this variable.
Then you must be thinking that since setting register_globals to ON has such convenient benefits, why not use it? Because if you do this it will cause a lot of security problems, and it may also conflict with local variable names.
For example, take a look at the following code:
if( !empty( $_POST['username'] ) && $_POST['username'] == ‘test123′ && !empty( $_POST['password'] ) && $_POST['password'] == “pass123″ ) { $access = true; }
If register_globals is set to ON during runtime, then the user only needs to pass access=1 in a query string to get whatever the PHP script runs.
Disable global variables in .htaccess
php_flag register_globals 0
Disable global variables in php.ini
register_globals = Off
Disable Magic Quotes like magic_quotes_gpc, magic_quotes_runtime, magic_quotes_sybase
Setting
in .htaccess filephp_flag magic_quotes_gpc 0 php_flag magic_quotes_runtime 0
Set in php.ini
magic_quotes_gpc = Off magic_quotes_runtime = Off magic_quotes_sybase = Off
Of course you can also validate user input. First you must know the data type you expect the user to input. In this way, you can be prepared on the browser side to prevent users from maliciously attacking you.
In web applications, it is simple to accept user input in the form and then feedback the results. When accepting user input, it would be very dangerous to allow HTML format input, because this would also allow JavaScript to intrude in unpredictable ways and execute directly. Even if there is only one such vulnerability, cookie data may be stolen and the user's account may be stolen.
PHP basically does not provide any tools to protect your database, so when you connect to the database, you can use the following mysqli_real_escape_string function.
$username = mysqli_real_escape_string( $GET['username'] ); mysql_query( “SELECT * FROM tbl_employee WHERE username = ’”.$username.“‘”);
Okay, in this short article, we elaborate on several PHP security issues that cannot be ignored during the development process. But it is ultimately up to the developer to decide whether to use it and how to use it. Hope this article can help you.