IP Library Granted Patent US 8,365,290
Granted Patent B2
US 8,365,290 · App. 12/466,728 · Granted Jan 29, 2013

Web application vulnerability scanner

Inventor: Frederick Young (Atlanta, GA)
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,365,290
App. No.
12/466,728
Granted
Jan 29, 2013
Kind
B2
Abstract

Disclosed is a method for quickly indentifying vulnerabilities in web applications. The method determines website links of interest and evaluates sites for web application vulnerabilities. Both in the selection of links and in their evaluation the method employs various heuristics to enforce a fast evaluation while requiring minimal resources to run.

Claims (40)

1. A method of detecting website vulnerabilities, comprising the steps of;

connecting to a website;

retrieving a webpage from the website;

identifying a link within the retrieved webpage;

comparing the identified link to a known database of links to determine a unique link, wherein determining the unique link includes evaluating a degree of uniqueness when compared to the known database;

requesting the unique link from a server;

generating an attack string directed to the requested unique link; and

identifying security vulnerabilities within the requested unique link.

2. The method of detecting website vulnerabilities of claim 1 , further including ending the retrieval of webpages and identification of links therein upon the occurrence of an end condition.

3. The method of detecting website vulnerabilities of claim 2 , wherein the end conditions are selected from the group consisting essentially of a time based event, a determined number of examined links event and a lack of new webpages to crawl.

4. The method of detecting website vulnerabilities of claim 3 , wherein the time based event is between about 5 to 15 minutes.

5. The method of detecting website vulnerabilities of claim 3 , wherein the determined number of examined links event is between about 300 to 700 links.

6. The method of detecting website vulnerabilities of claim 1 , wherein the generated attack string instructs to evoke a plurality errors.

7. The method of detecting website vulnerabilities of claim 6 , wherein the generated attack string instructs a plurality of errors is selected from two or more of the vectors groups essentially consisting of structured query languages (SQL), cross-site scripting (XSS), remote file inclusion (RFI) and combinations thereof.

8. The method of detecting website vulnerabilities of claim 1 , wherein the known database is comprised of links previously found and identified, and disposing of links determined not to be unique and characterizing and storing the unique links.

9. The method of detecting website vulnerabilities of claim 1 , further including comparing the determined uniqueness to a uniqueness threshold in determining the unique link.

10. A method of detecting website vulnerabilities, comprising the steps of;

connecting to a website;

retrieving a webpage from the website;

identifying a link within the retrieved webpage;

comparing the identified link to a known database of links to determine a unique link;

disposing of links determined not to be unique and characterizing and storing the unique links;

ending the retrieval of webpages and identification of links therein upon the occurrence of an end condition being selected from the group consisting essentially of a time based event of between about 5 to 15 minutes, a determined number of examined links event and a lack of new webpages to crawl;

requesting the unique link from a server;

generating an attack string directed to the requested unique link; and

identifying security vulnerabilities within the requested unique link.

11. The method of detecting website vulnerabilities of claim 10 wherein the determined number of examined links event is between about 300 to 700 links.

12. The method of detecting website vulnerabilities of claim 10 , wherein the generated attack string instructs to evoke a plurality errors.

13. The method of detecting website vulnerabilities of claim 12 , wherein the generated attack string instructs a plurality of errors is selected from two or more of the vectors groups essentially consisting of structured query languages (SQL), cross-site scripting (XSS), remote file inclusion (RFI) and combinations thereof.

14. The method of detecting website vulnerabilities of claim 10 , wherein determining the unique link includes evaluating a degree of uniqueness when compared to the known database, wherein the determined uniqueness to a uniqueness threshold in determining the unique link.

15. A method of detecting website vulnerabilities, comprising the steps of;

connecting to a website;

retrieving a webpage from the website;

identifying a link within the retrieved webpage;

comparing the identified link to a known database of links to determine a unique link, wherein determining the unique link includes evaluating a degree of uniqueness when compared to the known database and disposing of links not determined to be unique and characterizing and storing the unique links; ending the retrieval of webpages and identification of links therein upon the occurrence of an end condition selected from the group consisting essentially of a time based event, a determined number of examined links event and a lack of new webpages to crawl;

requesting the unique link from a server;

generating an attack string directed to the requested unique link, wherein the generated attack string instructs a plurality of errors is selected from two or more of the vectors groups essentially consisting of structured query languages (SQL), cross-site scripting (XSS), remote file inclusion (RFI) and combinations thereof; and

identifying security vulnerabilities within the requested unique link.

16. The method of detecting website vulnerabilities of claim 15 , further including comparing the determined uniqueness to a uniqueness threshold in determining the unique link.

17. The method of detecting website vulnerabilities of claim 15 , wherein the time based event is between about 5 to 15 minutes and the determined number of examined links event is between about 300 to 700 links.

Assignments (5)
SECURITY INTEREST Recorded Jul 6, 2016
From: CONTROLSCAN, INC.
To: HORIZON TECHNOLOGY FINANCE CORPORATION
Reel/Frame 039082/0478 →
RELEASE OF SECURITY INTEREST Recorded Jul 6, 2016
From: ESCALATE CAPITAL PARTNERS SBIC I, L.P.
To: CONTROLSCAN, INC.
Reel/Frame 039088/0170 →
SECURITY AGREEMENT Recorded Jan 22, 2014
From: CONTROLSCAN, INC.
To: ESCALATE CAPITAL PARTNERS SBIC I, L.P.
Reel/Frame 032112/0138 →
SECURITY AGREEMENT Recorded Jan 8, 2014
From: CONTROLSCAN, INC.
To: SILICON VALLEY BANK
Reel/Frame 031946/0458 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 2, 2009
From: YOUNG, FREDERICK
To: CONTROLSCAN INC.
Reel/Frame 022766/0712 →
Continuity (1)
Related Publication 20100293616A1 · Nov 18, 2010