Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Save to My Library
Look up keyword
Like this
21Activity
0 of .
Results for:
No results containing your search query
P. 1
Blind SQL Injection

Blind SQL Injection

Ratings:

4.8

(5)
|Views: 2,875 |Likes:
Published by Eddie Awad
Blind SQL Injection. Are your web applications vulnerable?
Blind SQL Injection. Are your web applications vulnerable?

More info:

Published by: Eddie Awad on Mar 28, 2007
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

02/27/2013

pdf

text

original

 
 
Start Secure. Stay Secure.™
 
Blind SQL Injection
Are your web applications vulnerable?
 
By SPI Labs
 
 
 
Start Secure. Stay Secure.™
 
© 2007 SPI Dynamics, Inc. All Rights Reserved.No reproduction or redistribution without written permission.
ii
Blind SQL Injection
Table of Contents
Introduction 3
 
What is Blind SQL Injection? 4
 
Detecting Blind SQL Injection 5
 
Exploiting the Vulnerability 7
 
Solutions 9
 
Parameterized Queries 10
 
Stored Procedures 12
 
Data Sanitization 15
 
Database Considerations 16
 
About SPI Labs 17
 
Contact Information 18
 
 
 
Start Secure. Stay Secure.™
 
© 2007 SPI Dynamics, Inc. All Rights Reserved.No reproduction or redistribution without written permission.
3
Blind SQL InjectionIntroduction
SQL Injection occurs when an application does not properly validate user-supplied input and then includes that input as part of a SQL statement. In alarge measure, SQL Injection depends on an attacker discovering andverifying portions of the original SQL query using information gained fromerror messages. However, web applications can still be vulnerable to BlindSQL Injection attacks even when error messages are not presented, or whenthey only reveal generic information. By altering the input parameters, anattacker can pose various “true-false” statements to the application to gatherinformation about the database and then ultimately reconstruct the SQLstatement by gauging its behavior. Are different pages displayed as a resultof changed input? Does an inserted “wait” command cause the application topause before responding? The “blind” portion of this comes from the fact thatno significant error was presented, yet the application is still vulnerable. BlindSQL Injection is no less dangerous than SQL Injection, and can have thesame devastating consequences. The objective of this paper is to educatesecurity professionals and developers on the techniques that can be used totake advantage of a web application that is vulnerable to Blind SQL Injection,and to make clear the correct mechanisms that should be put in place toprotect against Blind SQL Injection and similar input validation problems.

Activity (21)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
Kj FivǝAbi liked this
raj91188 liked this
Ifrit Raynskii liked this
Ak Hilal liked this
nwn866 liked this
nwn866 liked this

You're Reading a Free Preview

Download
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->