Projects: Security - Baseline
Home arrow Projects: Security arrow Page 2 - Testing for Web Site Vulnerabilities













Renew Your Subscription

Projects: Security



Testing for Web Site Vulnerabilities



By Regina Kwon

  Table of Contents:
  1. Testing for Web Site Vulnerabilities
  2. ' Testing for SQL Injection '
  3. ' Testing for Cross'
  4. ' Testing for Unrestricted Directory '

Will your Web site pass our security tests?

Rate This Article:
Add This Article To:

Testing for Web Site Vulnerabilities - ' Testing for SQL Injection '


( Page 2 of 4 )

Vulnerability">
Testing for SQL Injection Vulnerability

Step 1. Open the Web site in a browser.

Step 2. Find a script.
 align=Look for common scripting-language file extensions--Microsoft Active Server Pages (*.asp) and Macromedia ColdFusion (*.cfm) scripts are usually the most vulnerable. The search field is your best bet; the Uniform Resource Locator (URL) on the results page will likely contain a script. Also try hovering your cursor over links while watching the bottom status bar. If the status bar doesn't display URLs, click on links and watch the address bar until you find a URL that has parameters.

Step 3. Begin testing.
Once you are on a page whose URL contains parameters, you are ready to test for SQL Injection vulnerability. There are two methods. Be sure to test each parameter value, one at a time, with each method.

Method 1. In the address bar URL, highlight a paramter value. Replace it with a single quote.

><br>
<img src=Method 2. Instead of highlighting the entire parameter value, click inside the value and type a single quote.

><br>

<br><br>
<div class=Step 4. Send request.
Press the Enter or Return key. This will send your request to the Web server.

Step 5. Look for database error message.
Most will look similar to the examples below.

Example 1.

>
<br><br>
Sometimes the error message does not display on screen. To find it, you may have to search the HTML source of the page. (View | Source in Microsoft Internet Explorer or 
View | Page Source in Netscape.) A document will open. Use that program's search tool to look for either of these phrases:
<br><br>
<pre>Microsoft OLE DB</pre> or <pre>[ODBC]</pre>
<br>
<div class= Step 6. Learn more. If you see one of the error messages shown or find Microsoft OLE DB or [ODBC] in the source code, then the site is vulnerable to SQL Injection. Read SPI Dynamics' SQL Injection white paper for advice on how to fix this vulnerability.



 
 
>>> More Projects: Security Articles          >>> More By Regina Kwon
 


Sponsored Links
  • Get up and running in as quickly as 30 days with BI. Learn how today.

  • FREE Securing Smartphones & Tablets for Dummies Book from Sophos
  • 5 New Technologies That Will Change Enterprise ITAdvertisement
  • Build an IT Infrastructure That Delivers the Future
     
  •  
    FEATURED SPONSORED ARTICLES

    FEATURED SPONSORED VIDEOS

     



    LATEST STORIES


     

     


    Advertisement
    rss graphic
           Baseline Newsletters