SQLServer SQL Injection
SQL injection sample
Assuming the call to your web application's login handler looks like this:
Now in login.ashx, you read these values:
and query your database to determine whether a user with that password exists.
So you construct an SQL query string:
This will work if the username and password do not contain a quote.
However, if one of the parameters does contain a quote, the SQL that gets sent to the database will look like this:
This will result in a syntax error, because the quote after the d in d'Alambert ends the SQL string.
You could correct this by escaping quotes in username and password, e.g.:
However, it's more appropriate to use parameters:
If you do not use parameters, and forget to replace quote in even one of the values, then a malicious user (aka hacker) can use this to execute SQL commands on your database.
For example, if an attacker is evil, he/she will set the password to
and then the SQL will look like this:
Unfortunately for you, this is valid SQL, and the DB will execute this!
This type of exploit is called an SQL injection.
There are many other things a malicious user could do, such as stealing every user's email address, steal everyone's
password, steal credit card numbers, steal any amount of data in your database, etc.
This is why you always need to escape your strings.
And the fact that you'll invariably forget to do so sooner or later is exactly why you should use parameters.Because
if you use parameters, then your programming language framework will do any necessary escaping for you.
simple injection sample
If the SQL statement is constructed like this:
Then a hacker could retrieve your data by giving a password like pw' or '1'='1; the resulting SQL statement will be:
This one will pass the password check for all rows in the Users table because '1'='1' is always true.
To prevent this, use SQL parameters: