Home/ Questions/Q 79871
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T21:12:49+00:00

I’ve been preaching both to my colleagues and here on SO about the goodness

  • 0

I’ve been preaching both to my colleagues and here on SO about the goodness of using parameters in SQL queries, especially in .NET applications. I’ve even gone so far as to promise them as giving immunity against SQL injection attacks.

But I’m starting to wonder if this really is true. Are there any known SQL injection attacks that will be successfull against a parameterized query? Can you for example send a string that causes a buffer overflow on the server?

There are of course other considerations to make to ensure that a web application is safe (like sanitizing user input and all that stuff) but now I am thinking of SQL injections. I’m especially interested in attacks against MsSQL 2005 and 2008 since they are my primary databases, but all databases are interesting.

Edit: To clarify what I mean by parameters and parameterized queries. By using parameters I mean using ‘variables’ instead of building the sql query in a string.
So instead of doing this: 

SELECT * FROM Table WHERE Name = 'a name'

We do this:

SELECT * FROM Table WHERE Name = @Name

and then set the value of the @Name parameter on the query / command object.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Placeholders are enough to prevent injections. You might still be open to buffer overflows, but that is a completely different flavor of attack from an SQL injection (the attack vector would not be SQL syntax but binary). Since the parameters passed will all be escaped properly, there isn’t any way for an attacker to pass data that will be treated like ‘live’ SQL.

    You can’t use functions inside placeholders, and you can’t use placeholders as column or table names, because they are escaped and quoted as string literals.

    However, if you use parameters as part of a string concatenation inside your dynamic query, you are still vulnerable to injection, because your strings will not be escaped but will be literal. Using other types for parameters (such as integer) is safe.

    That said, if you’re using use input to set the value of something like security_level, then someone could just make themselves administrators in your system and have a free-for-all. But that’s just basic input validation, and has nothing to do with SQL injection.

    • 0