This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Difference between revisions of "Query Parameterization Cheat Sheet"

From OWASP
Jump to: navigation, search
m
(Parameterized Query Examples)
Line 12: Line 12:
 
= Parameterized Query Examples =
 
= Parameterized Query Examples =
  
SQL Injection is best prevented through the use of [[SQL_Injection_Prevention_Cheat_Sheet#Defense_Option_1:_Prepared_Statements_.28Parameterized_Queries.29|''parameterized queries'']]. The following chart demonstrates, with real-world code samples, how to build parameterized queries in most of the common web languages. The purpose of these code samples is to demonstrate to the web developer how to avoid SQL Injection when building database queries within an web application.
+
SQL Injection is best prevented through the use of [[SQL_Injection_Prevention_Cheat_Sheet#Defense_Option_1:_Prepared_Statements_.28Parameterized_Queries.29|''parameterized queries'']]. The following chart demonstrates, with real-world code samples, how to build parameterized queries in most of the common web languages. The purpose of these code samples is to demonstrate to the web developer how to avoid SQL Injection when building database queries within a web application.
  
 
{| class="wikitable nowraplinks"
 
{| class="wikitable nowraplinks"
Line 94: Line 94:
 
  '''my $sth = $dbh->prepare( $sql );'''
 
  '''my $sth = $dbh->prepare( $sql );'''
 
  '''$sth->execute( $bar, $baz );'''
 
  '''$sth->execute( $bar, $baz );'''
 +
|}
 +
 +
The SQL you write in your web application isn't the only place that SQL injection vulnerabilities can be introduced. If you are using Stored Procedures, and you are dynamically constructing SQL inside them, you can also introduce SQL injection vulnerabilities. To ensure this dynamic SQL is secure, you can parameterize this dynamic SQL too using bind variables. Here are some examples of using bind variables in stored procedures in different databases:
 +
 +
{| class="wikitable nowraplinks"
 +
|-
 +
! Language - Library
 +
! Parameterized Query
 +
|-
 +
| Oracle - PL/SQL
 +
|
 +
Normal Oracle Stored Procedure - no dynamic SQL being created. Parameters passed in to stored procedure are naturally bound to their location within the query without anything special being required.
 +
 +
  PROCEDURE usp_SafeGetBalanceQuery(
 +
    UserID varchar, Dept varchar) AS BEGIN
 +
 
 +
    SELECT balance FROM accounts_table WHERE user_ID = UserID AND
 +
      department = Dept;
 +
  END;
 +
 +
|-
 +
| Oracle - PL/SQL
 +
 +
Stored Procedure Using Bind Variables in Dynamic SQL Run with EXECUTE IMMEDIATE. Bind variables are used to tell the database that the inputs to this dynamic SQL are 'data' and not possibly 'code'.
 +
 +
  PROCEDURE usp_AnotherSafeGetBalanceQuery(
 +
    UserID varchar, Dept varchar) AS
 +
    stmt VARCHAR(400); result NUMBER;
 +
 
 +
  BEGIN
 +
    stmt := 'SELECT balance FROM accounts_table WHERE user_ID = :1
 +
      AND department = :2';
 +
    EXECUTE IMMEDIATE stmt INTO result USING UserID, Dept;
 +
    RETURN result;
 +
  END;
 
|}
 
|}
  

Revision as of 00:02, 6 June 2014

Cheatsheets-header.jpg

Last revision (mm/dd/yy): 06/6/2014

Introduction

SQL Injection is one of the most dangerous web vulnerabilities. So much so that it's the #1 item in the OWASP Top 10. It represents a serious threat because SQL Injection allows evil attacker code to change the structure of a web application's SQL statement in a way that can steal data, modify data, or potentially facilitate command injection to the underlying OS. This cheat sheet is a derivative work of the SQL Injection Prevention Cheat Sheet.

Parameterized Query Examples

SQL Injection is best prevented through the use of parameterized queries. The following chart demonstrates, with real-world code samples, how to build parameterized queries in most of the common web languages. The purpose of these code samples is to demonstrate to the web developer how to avoid SQL Injection when building database queries within a web application.

The SQL you write in your web application isn't the only place that SQL injection vulnerabilities can be introduced. If you are using Stored Procedures, and you are dynamically constructing SQL inside them, you can also introduce SQL injection vulnerabilities. To ensure this dynamic SQL is secure, you can parameterize this dynamic SQL too using bind variables. Here are some examples of using bind variables in stored procedures in different databases:

Authors and Primary Editors

Jim Manico - jim [at] owasp.org
Dave Wichers - dave.wichers [at] aspectsecurity.com
Neil Matatal - neil [at] owasp.org

Other Cheatsheets