Mar 21, 2013
Try to use the class Parameters from the db object.
This class prevent about injection.
Aug 02, 2013
Based on the above answers, I think we have to be a bit more careful when presenting solutions that prevent Sql Injection because the damage done can be large.
- Stored procedures are NOT a solution.
A procedure that performs string concatenation is highly vulnerable to Sql injection.
- Re-validate data in Stored Procedure is NOT a solution.
I am not even sure what kind of validation to do. Disallow certain keywords? How and which ones? It is almost impossible to catch all possible attacks.
- Use parameterized queries.
Indeed, using SQL Parameters is a very good way to prevent Sql injection.
- Use ORM tools (LINQ, NHibernate, LINQ to Entities)
First of all, LINQ is not an ORM tool - I am not sure how this helps in Sql injection.
With LINQ to Entities, I guess you mean Entity Framework.
Yes, using a proven ORM tool such as NHibernate and Entity Framework are good solutions.
But you should not pass any user input concatenated into Sql strings directly to these tools.
- Use regular expression to discard input string
Yes, you can create a black-list of keywords that are not allowed, or a white-list of expressions that are allowed.
However, this should be in combination with SQL Parameters or a proven ORM.
The link you provided is also giving bad advice: http://cybarlab.blogspot.com/2013/04/how-to-prevent-sql-injection.html