US 6,996,845 B1Grant
Internet security analysis system and process
Issue Date:2006-02-07
•66 Claims
•3 Drawing Sheets
Abstract
An automated Web security analysis system and process identifies security vulnerabilities in a target Internet Web site by parsing through the target Web site to search for a predetermined list of common security vulnerabilities. The process is recursive, exploiting information gathered throughout the process to search for additional security vulnerabilities. A prioritized list of detected security vulnerabilities is then presented to a user, including preferably a list of recommendations to eliminate the detected security vulnerabilities.
Metadata
Assignee
- S.P.I. Dynamics Incorporated
Inventors
- Dennis Wayne Hurst
- Darrin Ray Barrall
- Caleb Ikaki Sima
Application Information
Application Number:US 09/722,655
Filing Date:2000-11-28
Priority Date:2000-11-28
Art Unit:2137
Classifications
IPC:
G06F11/30
Patent Drawings (3 sheets)
Description
Background of the Invention
[0001] 1) Field of the Invention
[0002] This invention pertains to the field of computer security, and more particularly, to a system and process for analyzing potential security flaws in an Internet Web site.
[0003] 2) Description of the Related Art
[0004] Increasingly, Internet Web sites are being exposed to external attack, or “hacking,” which has been defined as the act of penetrating a closed computer system to gain access to knowledge and information that is contained within. Individuals attack Web sites for a variety of reasons. A report by the United States Federal Bureau of Investigation (FBI) indicates that the originators of proprietary information theft can be classified into six categories. The report shows 35% of the criminals were discontented employees, 28% hackers, 18% other U.S. companies, 11% foreign companies, 8% foreign governments, and 10% miscellaneous. Examples of some well-known attack methods include e-mail bombing, denial-of-service attacks, Trojan horses, worms, and simple back-door entry to a Web site. These attacks can not only cripple or shut down access to an attacked Web site, but can result in unauthorized access to confidential customer information, including access passwords, and even credit card account numbers. The resulting damage to a commercial Web site can easily run into the millions of dollars.
[0005] According to the most recent FBI report, cyber crimes increased from 547 in 1998 to 1,154 in 1999. The FBI and the Computer Security Institute (Silicon Valley) found that 62% of information security officials reported security breaches in 1999 (National Journal's Technology Daily). These break-ins resulted in $123 million losses from fraud, information theft, sabotage, and viruses.
[0006] Many companies use a proprietary base software product for conducting business and are focusing on tools for managing risk, and controlling sabotage against their applications. According to a Cyber-source study of online E-tailors, 75% consider fraud to be a problem, and 62% consider it to be a serious problem. The NIPC, FBI, and United States Treasury, along with the President, have committed themselves to working along side the private sector in putting these concerns to rest. Both the Economic Espionage Act of 1996, and the Theft of Trade Secrets Act (section 1832) have caused organizations to react promptly to damaging acts of violations.
[0007] Yet this problem is still not controlled and is in need of counter-measures. In January of 2000, several denial-of-service (DOS) attacks occurred to well known E-commerce Web sites such as YAHOO® and E-BAY®. Incidents like this have brought the issue of Web site security directly into the public limelight. Of all the individuals polled on the questions of online banking, 65% stated that security was the main concern.
[0008] Maintaining control of electronic fraud can be a time consuming process for E-commerce companies, banks, brokerage firms, and electronic billing/payment providers. Both the network administrators and Web-masters do not have the proper tools to detect Web-based vulnerabilities. The complexity of information, separate system options, assessing the significance of penetrations, and a decision for correction is not prevalent in today's workplace. On-line fraud has a special significance for an E-commerce site. The fear of security exploits can cause a negative impact on consumer confidence in an E-commerce site, which ultimately destroys the brand's image.
[0009] To prevent such attacks, Web site administrators manually search for and close potential security holes in their own Web sites. Because most Web sites undergo changes over time, and because new vulnerabilities and attack techniques are continually being developed, the Web site administrators must continually probe their sites for security weaknesses. This is time-consuming and fraught with the likelihood of undetected security flaws.
[0010] As the Internet continues to expand, more and more Web sites are being developed and operated by less experienced and trained personnel. And it becomes more and more difficult for all of these individuals to be knowledgeable in all of the latest techniques for hacking a Web site. This increases the potential for Web site security flaws to exist which can be exploited by hackers.
[0011] Accordingly, there is a need for an advanced Web security analysis system and process that can be used by Web site developers and administrators to identify security flaws in their Internet Web sites. It would also be advantageous to provide such a system and process which can be used by third party individuals who lack specific knowledge of an individual Web site's architecture and design. It would be further advantageous to provide such a system and process which is automated, and which performs a security check without significant manual user intervention. Other and further objects and advantages will appear hereinafter.
Summary of the Invention
[0012] The present invention comprises a system and process for analyzing potential security flaws in an Internet Web site.
[0013] In one aspect of the invention, an Internet security analysis system and process checks a target Internet Web site against a predetermined set of known exploits.
[0014] In another aspect of the invention, an Internet security analysis process is automated to execute without significant manual user interaction.
[0015] In yet another aspect of the invention, an Internet security analysis process is recursive, gathering information of security vulnerabilities and then exploiting that information to search for additional security vulnerabilities.
Brief Description of the Drawings
[0016] FIG. 1 is a functional block diagram
[0017] FIG. 2 is a flowchart of a method of parsing through a Web site to identify possible security holes;
Description of the Preferred Embodiments
[0018] In a preferred embodiment, an Internet security analysis process is initiated by a Web site administrator for a target Web site to be analyzed. The process may be executed by an Internet security analysis system, which may be a personal computer having Internet access to the target Web site. Alternatively, a user may conduct the Internet security process through an Internet security analysis Web site. In that case, the Internet analysis system may be accessible via a Web server hosting the Internet security analysis Web site. Other embodiments are possible.
[0019] FIG. 1 is a block diagram of a preferred embodiment of an Internet security analysis system 100 for performing a security analysis process for a target Web site. In a preferred embodiment, the Internet security analysis system 100 includes at least one central processing unit (CPU) 105 having associated therewith memory 110 and a mass data storage device 115, and optionally a display device 120, a data input device 125 (e.g., keyboard; mouse), and a network connection device 130, all connected to each other via a communication bus 135. The data storage device 115 includes nonvolatile data storage means, such magnetic disk drive units, optical disk drive units, removable disk drive units, tape media, or any combination thereof. The network connection device 130 includes hardware and software for establishing a data link connection between the Internet security analysis system 100 and a target Web site via the Internet. Preferably, the network connection device 130 includes circuitry to tie directly to the Internet via T1, T4 or similar high bandwidth data lines as would be understood by one skilled in the art.
[0020] The Internet security analysis system 100 may include two or more integrated computer units, each having a separate CPU 105 having associated therewith memory 110 and/or a mass data storage device 115, and optionally a display device 120 and a data input device (e.g., keyboard; mouse) 125. The communication bus 135 may include two or more internal buses for integrated computer units, together with an external bus connecting two or more integrated computer units.
[0021] In a preferred embodiment, the Internet security analysis system 100 executes one or more software routines to perform an automatic security analysis process. The automatic security analysis process analyzes a target Web site to identify security flaws. Preferably, the security analysis process executes a method of parsing through a target Web site to search for common security flaws. For example, in a preferred embodiment, the method includes analyzing the hyper-text markup language (HTML) script for the Web pages of the Web site and searching for commented-out references. Such commented-out references may include uniform resource locators (URLS) of Internet addresses for Web pages or other objects which are not intended to be accessed by a visitor to the Web site. Such Web pages or objects may contain data resident on a server hosting the target Web site which is not intended to be available to a visitor. As another example, in a preferred embodiment, the method includes bombarding the data entry fields of any Web forms of the target Web site with data in an attempt to break the target Web site.
[0022] A flowchart for a preferred embodiment process 200 of automatically parsing through a target Web site to identify possible security holes is shown in FIG. 2 . The process 200 may be initiated by a user and executed by a software program running on the Internet security analysis system 100, which as described above may be preferably a standalone user computer, or a computer accessible to a user via the Internet, etc. Typically, the process 200 is initiated by an administrator of the target Web site.
[0023] In a first step 205, an Internet security analysis computer establishes an Internet connection with a Web server hosting an Internet Web site for which a security inspection will be performed (the “target Web site”). The Internet security analysis computer retrieves a default Web page for the target Web site, e.g., “Index.html.”
[0024] In a step 210, the Internet security analysis system 100 parses through the script (e.g., HTML code) for the default Web page to search for any linked-to Web pages or other objects which are referenced. The URL or address of each linked-to Web page is then stored in a database at the Internet security analysis computer. In particular, the Internet security analysis computer parses through Web pages looking for anchor links and JAVASCRIPT® links.
[0025] In a step 215, each linked-to Web page is then in turn retrieved by the Internet security analysis computer and the script for the retrieved Web page is parsed to search for any further linked-to Web pages. This process is repeated for each link and each linked-to Web page that is found. Preferably, the “depth” of linked-to Web pages which are retrieved may be set by a user to any value, so that only first or second level linked-to Web pages may be retrieved. Alternatively, only linked-to Web pages which are hosted on a same server, or which have a same domain address, as the default Web page may be retrieved.
[0026] As a result of the steps 205–215, the Internet security analysis system builds a valid Web page database with an entire map of the valid Web pages of the target Web site.
[0027] Then, in a step 220, the default Web page for the target Web site is parsed for any hidden Uniform Resource Locators (URLs), such as commented-out code, or any reference to a file or Web page that is not linked-to (or HREF'ed). These hidden URLs are then checked against the valid Web page database to insure that the Internet security analysis system has not already retrieved the corresponding hidden Web page or object. If the corresponding hidden Web page or object has not previously been retrieved, then the address is stored in a prioritized database of “vulnerable” Web pages at the Internet security analysis computer.
[0028] In a step 225, each hidden Web page or object is then in turn retrieved by the Internet security analysis system and the script is parsed to search for any further hidden URL's. If any further hidden URL's are found, then the Internet security analysis system retrieves the corresponding hidden Web page or object for the hidden URL and parses through it to search for any still further hidden URLs. This process is repeated for each link and each linked-to Web page or object that is found.
[0029] As a result of the steps 220–225, the Internet security analysis system builds a vulnerable Web page database with an entire map of the “vulnerable” Web pages of the target Web site. Together, the steps 205–225 constitute a “Webcrawl” of the entire target Web site, performed by parsing through each retrieved Web page in turn to find additional links.
[0030] Preferably, when the Internet security analysis system 100 parses through each retrieved Web page, it performs a keyword search to detect points of interest. For instance, if a Web page is retrieved thru the Webcrawl with the word “admin” located in the Web page, the Internet security analysis system 100 will flag it as a “point of interest” and name it as “possible administration Web page.”
[0031] Then, in a step 230, the Internet security analysis system 100 checks a predetermined—but extensible—list of known, common security vulnerabilities. Typically, these security vulnerabilities are “exploits” which have become well known to security experts. The Internet security analysis system scans the target Web site to determine whether or not any of the exploits are present at the target Web site.
[0032] For example, assume a case where the following three security vulnerabilities are to be checked:
- [0033] /security/exploit.asp
- [0034] /security/vuln.asp
- [0035] /security/b00m.asp
[0036] In that case, the Internet security analysis system will issue a request to the target Web site for the directory “security.” The Web server for the target Web site will issue either a true or false response, depending on whether the directory exists or not. If the response is true (indicating that the directory does exist), then the above-mentioned three security vulnerabilities are checked to determine whether they exist.
[0037] In the above case, it is also possible to perform a keyword search on each response received to detect points of interest. For instance, if a response is received with the keyword “<DIR>” included, the Internet security analysis system 100 will flag it as a vulnerability.
[0038] As another example, assume that the “Webcrawl” in the steps 205–225 retrieved the URL “/scripts/db/msadcs.dll” and stored it in the vulnerable Web pages database, and that “/msadc/msadcs.dll” is stored in the list of known, common security vulnerabilities. In that case, in the step 230, the Internet security analysis system 100 takes the actual filename of the check (msadcs.dll) and flags it as being present in “/scripts/db/msadcs.dll.” This allows the Internet security analysis system 100 to find a security vulnerability even though it is out of its normal location. Once a security vulnerability is found in an alternate directory the Internet security analysis system 100 will check for other files that typically reside with the file that was found. For example, if “msadcs.dll” is usually in a folder that also contains “msadcs2.dll”, then the Internet security analysis system 100 would also check for the existence of “msadcs2.dll” in the “/scripts/db” folder where “msadcs.dll” was found.
[0039] Another security vulnerability check which may be employed by the Internet security analysis system 100 is common file name checking. For example, the Internet security analysis system 100 will recursively try to request WS_FTP.LOG from all directories retrieved from the Webcrawl.
[0040] Yet another security vulnerability check which may be employed by the Internet security analysis system 100 is port scanning (scanning a machine for open ports) integrated with Web server discovery. By taking the information retrieved from a port scanner (port open on any given host) the Internet security analysis system 100 will attempt to determine whether that port is supporting HTTP or HTTPS. If the port returns valid on any HTTP or HTTPS request then the server is marked as a Web server sitting on that specific port. The Internet security analysis system 100 will go through an entire range of hosts, trying each port with this method. When completed, the Internet security analysis system 100 will have a list of hosts that are currently hosting a Web server and the port or ports on which the Web server is listening. The Internet security analysis system 100 will then take this list and pass it to the “Webcrawl engine” portion of the Internet security analysis system 100. This allows an easy ability to scan an entire network and look for Web vulnerabilities.
[0041] If a security vulnerability exists, then in a step 235 a record of the security vulnerability is added to a security vulnerability database maintained at the Internet security analysis system 100.
[0042] Accordingly, an efficient and intelligent vulnerability search is conducted. Because a Web site may be very large and contain hundreds or more Web pages and dozens or more exploits must be checked, the above-described process of determining the appropriateness of a security check before actually issuing the check greatly expedites the automated security check process.
[0043] Advantageously, in a step 240 the Internet security analysis system further exploits each of the vulnerabilities detected in the step 235 and added to the security vulnerability database to search for further security vulnerabilities and to gather other information regarding the target Web site. This process is recursively repeated until no new data is obtained.
[0044] In a step 245, the Internet security analysis system applies a predetermined—but extensible—list of hack methods to the data which was retrieved in the steps 205–240 to identify security vulnerabilities.
[0045] In a preferred embodiment, a first hack method comprises the Internet security analysis system issuing a series of requests, such as:
- [0046] GET/$SERVER_NAME/$SCRIPT_NAME?$VAR1=/../../../boot.ini
- [0047] GET/$SERVER_NAME/$SCRIPT_NAME?$VAR2=/../../../boot.ini
- [0048] .
- [0049] .
- [0050] .
These requests check every script name and variable at the target Web site for a “Directory traversal exploit.” If any of these requests return a positive result, then a security vulnerability has been found.
[0051] In a second hack method, the Internet security analysis system searches for buffer overflows by issuing a series of requests such as:
- [0052] GET/$SERVER_NAME/$SCRIPT_NAME?$VAR1=AAAAAAA . . . (2048 more A'S)
- [0053] GET/$SERVER_NAME/$SCRIPT_NAME?$VAR2=AAAAAAA . . . (2048 more A'S)
- [0054] .
- [0055] .
- [0056] .
These requests check every script name and variable at the target Web site for unexpected results in the case of a buffer overflow. If any unexpected data is returned, then a security vulnerability has been found.
[0057] In a third hack method, the Internet security analysis system searchs for old files or variables which are still present on a web server for the target Web site, but which are not intended to be available to a visitor. The Internet security analysis system searches issues a series of requests such as:
- [0058] GET/$SERVER_NAME/$SCRIPT_NAME.old
- [0059] GET/$SERVER_NAME/$SCRIPT_NAME.bak
- [0060] GET/$SERVER_NAME/$SCRIPT_NAME.bac
These requests are issued for every script name and variable at the target Web site.
[0061] Although a preferred embodiment process includes the three hack methods described above, additional hack methods are also possible and may be employed.
[0062] For example, where the Web site includes a Web form, intentionally invalid data may be entered into one or more data entry fields of the Web form and submitted to the Web site to determine if any invalid or unexpected results are produced by the Web site. This process may recursively submit various combinations of invalid data entered into the various data entry fields of the Web form. Once a security vulnerability is detected in this way, the data producing the vulnerability may then be used as a starting point for testing all other Web forms at the target Web site.
[0063] Preferably, a user may also employ cookie or HTML manipulation to search for security vulnerabilities. The Internet security analysis system 100 will allow a user to intercept the communication between a browser and a Web server and give the user the option to change or manipulate the data being sent between the client and server before the data is actually sent. This allows a user to manipulate the communication in any way, including cookies and over SSL communication. The Internet security analysis system 100 allows a user to create an HTTP or HTTPS request from either an existing request that has already been send to the server or to create a new request on the fly, including the ability to add, modify or not send any of the following: the URL; parameters that are sent to the server; any Header that is sent in the request; cookies that are sent to the server; and the method that is used to send the request (i.e.: HEAD, POST, GET).
[0064] If during the Webcrawl in the steps 205–225, the Internet security analysis system 100 encounters what it deems to be a login page, it will give the option to the user to “brute force” the login (try multiple logins and passwords until a successful one is retrieved), or to automate the login so that the Internet security analysis system 100 will brute force it automatically, and the user does not have to stop the scan and will brute force it automatically.
[0065] Preferably, there are two methods of brute forcing a login screen it can either be a form login or a basic authorization “pop-up box” login.
[0066] The Internet security analysis system 100 also preferably supports passing of user defined user names and passwords that are sent to the target server. This facilitates testing of target Web sites that require a login name and password to gain access to the target Web site, or a folder on the target Web site.
[0067] Moreover, in some cases one or more of the above-described hack methods may not be used. Optionally, the user may choose the hack methods which are employed.
[0068] If any of security vulnerabilities have been found in the step 245, then in a step 250 the Internet security analysis system adds a record for the security vulnerability to the security vulnerability database.
[0069] Finally, in a step 255, the Internet security analysis system prioritizes all security vulnerabilities which have been identified in the steps 205–250, and presents the prioritized list to the user, for example on a computer display screen. For example, it is known that a “SQL server error” is high risk vulnerability, and accordingly, this will be communicated to the user via the prioritization. Preferably, the Internet security analysis system also suggests how the user may eliminate the detected security vulnerabilities.
[0070] In a preferred embodiment, a user may disable the automatic operation and instead control one or more aspects of how the Internet security analysis process executes. For example, the user may be allowed to change the values sent to the target Web site in the step 245. The user may also view any malformed “cookies” which are returned during the Internet security analysis process. The user may manually edit and change the HTML code for any Web page which is retrieved from the Web site and then submit the changed Web page back to the server for the target Web site. This facilitates scanning of applications where specific user interaction (e.g., username and password) are required to gain access to the application, or where an automated scan could be dangerous to the application. One example of an application where an automated scan could be dangerous would be administrative application that has elevated access to the target Web site.
[0071] While preferred embodiments are disclosed herein, many variations are possible which remain within the concept and scope of the invention. Such variations would become clear to one of ordinary skill in the art after inspection of the specification, drawings and claims herein. The invention therefore is not to be restricted except within the spirit and scope of the appended claims.
Claims
Certificate of Correction present
The claims shown below may not include correction changes. Use the corrected PDF for authoritative text.
What is claimed is:
1. A process of detecting security vulnerabilities present in a target Web site, comprising:
establishing an Internet connection with the target Web site;
retrieving a default Web page for the target Web site;
parsing through the default Web page to identify any linked-to Web pages or objects which are included in the default Web page;
automatically passing an authorized username and password to the target Web site, if required to gain access to the target Web site;
scanning the target Web site for at least one known exploit in order to identify security vulnerabilities;
applying at least one predetermined hack method to the target Web site in order to identify security vulnerabilities; and
outputting the security vulnerabilities.
2. the method of claim 1, further comprising scanning at least one of the security vulnerabilities for at least one known exploit in order to identify further security vulnerabilities.
3. The method of claim 1, further comprising parsing through the linked-to Web pages to identify any further-linked-to Web pages or objects which are included in the linked-to Web pages.
4. The method of claim 3, further comprising parsing through the default Web page to identify any hidden Web pages or objects which are included in the hidden Web pages.
5. The method of claim 4, further comprising parsing through the hidden Web-pages to identify any further-hidden Web pages or objects which are included in the further-hidden Web pages.
6. The method of claim 5, further comprising:
comparing each hidden Web page and each further-hidden Web page to each linked-to Web page and each further-linked-to Web page; and
identifying each hidden Web page and each further-hidden Web page that is different from the linked-to Web pages and the further-linked to Web pages.
7. The method of claim 3, wherein the parsing through the default Web page and the parsing through the linked-to Web pages include performing a keyword search in order to detect at least one point of interest.
8. The method of claim 7, wherein the at least one point of interest is selected from the group consisting of an administration Web page and a directory list tag.
9. The method of claim 7, wherein the applying at least one predetermined hack method includes attempting to access unauthorized files located outside the target Web site's root directory.
10. The method of claim 3, wherein the applying at least one predetermined hack method includes attempting to access unauthorized files located outside the target Web site's root directory.
11. The method of claim 10, wherein the scanning the target Web site for at least one known exploit includes checking for at least one common filename.
12. The method of claim 11, wherein the at least one common filename is selected from the group consisting of “msadcs.dll” and “WS_FTP.LOG.”
13. The method of claim 3, wherein the applying at least one predetermined hack method includes automatically passing multiple usernames and passwords to the target Web site if a login Web page is encountered.
14. A process of detecting security vulnerabilities present in a target Web site, comprising:
establishing an Internet connection with the target Web site;
retrieving a default Web page for the target Web site;
parsing through the default Web page to identify any linked-to Web pages or objects which are included in the default Web page, wherein the parsing includes performing a keyword search in order to detect at least one point of interest;
scanning the target Web site for at least one known exploit in order to identify security vulnerabilities;
applying at least one predetermined hack method to the target Web site in order to identify security vulnerabilities; and
prioritizing the security vulnerabilities.
15. The method of claim 14, further comprising parsing through the default Web page to identify any hidden Web pages or objects which are included in the hidden Web pages.
16. The method of claim 15, further comprising parsing through the hidden Web-pages to identify any further-hidden Web pages or objects which are included in the further-hidden Web pages.
17. The method of claim 16, further comprising:
comparing each hidden Web page and each further-hidden Web page to each linked-to Web page and each further-linked-to Web page; and
identifying each hidden Web page and each further-hidden Web page that is different from the linked-to Web pages and the further-linked to Web pages.
18. The method of claim 14, further comprising parsing through the linked-to Web pages to identify any further-linked-to Web pages or objects which are included in the linked-to Web pages.
19. The method of claim 18, wherein the at least one point of interest is selected from the group consisting of an administration Web page and a directory list tag.
20. The method of claim 18, further comprising scanning at least one of the security vulnerabilities for at least one known exploit in order to identify further security vulnerabilities.
21. The method of claim 18, wherein the applying at least one predetermined hack method includes attempting to access unauthorized files located outside the target Web site's root directory.
22. The method of claim 18, further comprising automatically passing an authorized username and password to the target Web site, if required to gain access to the target Web site.
23. The method of claim 18, wherein the applying at least one predetermined hack method includes automatically passing multiple usernames and passwords to the target Web site if a login Web page is encountered.
24. The method of claim 18, wherein the applying at least one predetermined hack method includes passing invalid data to a data entry field of the target Web site and evaluating the result.
25. The method of claim 24, further comprising:
recording the invalid data which produces a security vulnerability; and
passing the recorded invalid data to at least one other data entry field of the target Web site.
26. A process of detecting security vulnerabilities present in a target Web site, comprising:
establishing an Internet connection with the target Web site;
retrieving a default Web page for the target Web site;
parsing through the default Web page to identify any linked-to Web pages or objects which are included in the default Web page;
scanning the target Web site for at least one known exploit in order to identify security vulnerabilities;
applying at least one predetermined hack method to the target Web site in order to identify security vulnerabilities, wherein the applying at least one predetermined hack method includes attempting to access unauthorized files located outside the target Web site's root directory; and
outputting the security vulnerabilities.
27. The method of claim 26, further comprising scanning at least one of the security vulnerabilities for at least one known exploit in order to identify further security vulnerabilities.
28. The method of claim 26, further comprising parsing through the linked-to Web pages to identify any further-linked-to Web pages or objects which are included in the linked-to Web pages.
29. The method of claim 28, further comprising parsing through the default Web page to identify any hidden Web pages or objects which are included in the hidden Web pages.
30. The method of claim 29, further comprising parsing through the hidden Web-pages to identify any further-hidden Web pages or objects which are included in the further-hidden Web pages.
31. The method of claim 30, further comprising:
comparing each hidden Web page and each further-hidden Web page to each linked-to Web page and each further-linked-to Web page; and
identifying each hidden Web page and each further-hidden Web page that is different from the linked-to Web pages and the further-linked to Web pages.
32. The method of claim 28, wherein the parsing through the default Web page and the parsing through the linked-to Web pages include performing a keyword search in order to detect at least one point of interest.
33. The method of claim 32, wherein the at least one point of interest is selected from the group consisting of an administrative Web page and a directory list tag.
34. The method of claim 33, further comprising automatically passing an authorized username and password to the target Web site, if required to gain access to the target Web site.
35. The method of claim 28, wherein the scanning the target Web site for at least one known exploit includes checking for at least one common filename.
36. The method of claim 35, wherein the at least one common filename is selected from the group consisting of “msadcs.dll” and “WS_FTP.LOG.”
37. A system for detecting security vulnerabilities present in a target Web site, comprising:
memory for storing:
a Web page database;
at least one exploit; and
a security vulnerability database; and
a processor connected to the memory and being configured to:
establish an Internet connection with the target Web site;
retrieve a default Web page for the target Web site;
parse through the default Web page to identify any linked-to Web pages or objects which are included in the default Web page;
automatically pass an authorized username and password to the target Web site, if required to gain access to the target Web site;
scan the target Web site for at least one known exploit in order to identify security vulnerabilities;
apply at least one predetermined hack method to the target Web site in order to identify security vulnerabilities; and
prioritize the security vulnerabilities.
38. The system of claim 37, wherein the processor is further configured to parse through the linked-to Web pages to identify any further-linked-to Web pages or objects which are included in the linked-to Web pages.
39. The system of claim 38, wherein the processor is further configured to scan at least one of the security vulnerabilities for at least one known exploit in order to identify further security vulnerabilities.
40. The system of claim 39, wherein the processor is further configured to parse through the default Web page to identify any hidden Web pages or objects which are included in the hidden Web pages.
41. The system of claim 40, wherein the processor is further configured to parse through the hidden Web-pages to identify any further-hidden Web pages or objects which are included in the further-hidden Web pages.
42. The system of claim 41, wherein the processor is further configured to:
compare each hidden Web page and each further-hidden Web page to each linked-to Web page and each further-linked-to Web page; and
identify each hidden Web page and each further-hidden Web page that is different from the linked-to Web pages and the further-linked to Web pages.
43. The system of claim 38, wherein the applying at least one predetermined hack method includes attempting to access unauthorized files located outside the target Web site's root directory.
44. The system of claim 43, wherein the parsing through the default Web page and the parsing through the linked-to Web pages include performing a keyword search in order to detect at least one point of interest.
45. The system of claim 44, wherein the at least one point of interest is selected from the group consisting of an administrative Web page and a directory list tag.
46. The system of claim 38, wherein the applying at least one predetermined hack method includes automatically passing multiple usernames and passwords to the target Web site if a login Web page is encountered.
47. A system for detecting security vulnerabilities present in a target Web site, comprising:
memory for storing:
a Web page database;
at least one exploit; and
a security vulnerability database; and
a processor connected to the memory and being configured to:
establish an Internet connection with the target Web site;
retrieve a default Web page for the target Web site;
parse through the default Web page to identify any linked-to Web pages or objects which are included in the default Web page, wherein the parsing includes performing a keyword search in order to detect at least one point of interest;
scan the target Web site for at least one known exploit in order to identify security vulnerabilities;
apply at least one predetermined hack method to the target Web site in order to identify security vulnerabilities; and
output the security vulnerabilities.
48. The system of claim 47, wherein the processor is further configured to scan at least one of the security vulnerabilities for at least one known exploit in order to identify further security vulnerabilities.
49. The system of claim 47, wherein the processor is further configured to parse through the linked-to Web pages to identify any further-linked-to Web pages or objects which are included in the linked-to Web pages.
50. The system of claim 49, wherein the at least one point of interest is selected from the group consisting of an administrative Web page and a directory list tag.
51. The system of claim 49, wherein the processor is further configured to parse through the default Web page to identify any hidden Web pages or objects which are included in the hidden Web pages.
52. The system of claim 51, wherein the processor is further configured to parse through the hidden Web-pages to identify any further-hidden Web pages or objects which are included in the further-hidden Web pages.
53. The system of claim 52, wherein the processor is further configured to:
compare each hidden Web page and each further-hidden Web page to each linked-to Web page and each further-linked-to Web page; and
identify each hidden Web page and each further-hidden Web page that is different from the linked-to Web pages and the further-linked to Web pages.
54. The system of claim 49, wherein the processor is further configured to automatically pass an authorized username and password to the target Web site, if required to gain access to the target Web site.
55. The system of claim 54, wherein the applying at least one predetermined hack method includes attempting to access unauthorized files located outside the target Web site's root directory.
56. The system of claim 49, wherein the applying at least one predetermined hack method includes passing invalid data to a data entry field of the target Web site and evaluating the result.
57. The system of claim 56, wherein the processor is further configured to:
record the invalid data which produces a security vulnerability; and
pass the recorded invalid data to at least one other data entry field of the target Web site.
58. A system for detecting security vulnerabilities present in a target Web site, comprising:
memory for storing:
a Web page database;
at least one exploit; and
a security vulnerability database; and
a processor connected to the memory and being configured to:
establish an Internet connection with the target Web site;
retrieve a default Web page for the target Web site;
parse through the default Web page to identify any linked-to Web pages or objects which are included in the default Web page;
scan the target Web site for at least one known exploit in order to identify security vulnerabilities;
apply at least one predetermined hack method to the target Web site in order to identify security vulnerabilities, wherein the applying at least one predetermined hack method includes attempting to access unauthorized files located outside the target Web site's root directory; and
output the security vulnerabilities.
59. The system of claim 58, wherein the processor is further configured to parse through the linked-to Web pages to identify any further-linked-to Web pages or objects which are included in the linked-to Web pages.
60. The system of claim 59, wherein the processor is further configured to parse through the default Web page to identify any hidden Web pages or objects which are included in the hidden Web pages.
61. The system of claim 60, wherein the processor is further configured to parse through the hidden Web-pages to identify any further-hidden Web pages or objects which are included in the further-hidden Web pages.
62. The system of claim 61, wherein the processor is further configured to:
compare each hidden Web page and each further-hidden Web page to each linked-to Web page and each further-linked-to Web page; and
identify each hidden Web page and each further-hidden Web page that is different from the linked-to Web pages and the further-linked to Web pages.
63. The system of claim 62, wherein the parsing through the default Web page and the parsing through the linked-to Web pages include performing a keyword search in order to detect at least one point of interest.
64. The system of claim 63, wherein the at least one point of interest is selected from the group consisting of an administration Web page and a directory list tag.
65. The system of claim 59, wherein the processor is further configured to automatically pass an authorized username and password to the target Web site, if required to gain access to the target Web site.
66. The system of claim 65, wherein the processor is further configured to scan at least one of the security vulnerabilities for at least one known exploit in order to identify further security vulnerabilities.
Patent Citations (43)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4975950(A) | 1990-12-01 | Lentz | Applicant |
| US5121345(A) | 1992-06-01 | Lentz | Applicant |
| US5421006(A) | 1995-05-01 | Jablon et al. | Applicant |
| US5440723(A) | 1995-08-01 | Arnold et al. | Applicant |
| US5454000(A) | 1995-09-01 | Dorfman | Applicant |
| US5509076(A) | 1996-04-01 | Sprunk | Applicant |
| US5557742(A) | 1996-09-01 | Smaha et al. | Applicant |
| US5621889(A) | 1997-04-01 | Lermuzeaux et al. | Applicant |
| US5684957(A) | 1997-11-01 | Kondo et al. | Applicant |
| US5699403(A) | 1997-12-01 | Ronnen | Applicant |
| US5795942(A) | 1998-08-01 | Esbensen | Applicant |
| US5805801(A) | 1998-09-01 | Holloway et al. | Applicant |
| US5842002(A) | 1998-11-01 | Schnurer et al. | Applicant |
| US5870559(A) | 1999-02-01 | Leshem et al. | Applicant |
| US5892903(A) | 1999-04-01 | Klaus | Applicant |
| US5919258(A) | 1999-07-01 | Kayashima et al. | Applicant |
| US5931946(A) | 1999-08-01 | Terada et al. | Applicant |
| US5958008(A) | 1999-09-01 | Pogrebisky et al. | Applicant |
| US5961644(A) | 1999-10-01 | Kurtzberg et al. | Applicant |
| US5974549(A) | 1999-10-01 | Golan | Applicant |
| US5982890(A) | 1999-11-01 | Akatsu | Applicant |
| US5983348(A) | 1999-11-01 | Ji | Applicant |
| US5991881(A) | 1999-11-01 | Conklin et al. | Applicant |
| US6044398(A) | 2000-03-01 | Marullo et al. | Applicant |
| US6138157(A) | 2000-10-01 | Welter et al. | Applicant |
| US6145003(A) | 2000-11-01 | Sanu et al. | Applicant |
| US6185689(B1) | 2001-02-01 | Todd et al. | Examiner |
| US6185701(B1) | 2001-02-01 | Marullo et al. | Applicant |
| US6584569(B2) | 2003-06-01 | Reshef et al. | Examiner |
| US6631408(B1) | 2003-10-01 | Welter et al. | Applicant |
| US2002/0023059(A1) | 2002-02-01 | Bari et al. | Examiner |
| DE3621106(A1) | 1968-01-01 | Applicant | |
| EP329415(A2) | 1989-08-01 | Applicant | |
| JP6324972(A2) | 1994-11-01 | Applicant | |
| JP7262135(A) | 1995-10-01 | Applicant | |
| JP11316677(A) | 1999-11-01 | Applicant | |
| WO98/42103 | 1998-09-01 | Applicant | |
| WO99/21335 | 1999-04-01 | Applicant | |
| WO99/35583 | 1999-07-01 | Applicant | |
| WO99/56195 | 1999-11-01 | Applicant | |
| WO99/56196 | 1999-11-01 | Applicant | |
| WO99/59292 | 1999-11-01 | Applicant | |
| WO99/68383 | 1999-12-01 | Applicant |
Non-Patent Literature (37)
- Garfinkel, Simson et al., “Secure CGI/API Programming,” www.w3journal.com, Excerpted from Web Security & Commerce, 1997, pp. 1-16, O'Reilly & Associates.Applicant
- Puppy, Rain Forest, “A lock at whisker's anti-IDS tactics: Just how bad can we ruin a good thing?,” www.wiretrip.net, pp. 1-8.Applicant
- “The ELZA ” and “The ELZA Project Manifesto,” www.stoev.org, pp. 1-4.Applicant
- Stewart, John N., “Tools for Web Security,” webserver.cpg.com, Jan. 1998, pp. 1-4.Applicant
- Mudge, “BoS: test-cgi problem,” www.tao.ca, Apr. 22, 1996, pp. 1-2.Applicant
- Puppy, Rain Forest, “Linux Weekly News,” old.lwn.net, Oct. 20, 1999, pp. 1-2.Applicant
- Farmer, Dan et al., “Improving the Security of Your Site by Breaking into it,” www.fish.com, 1993, pp. 1-18.Applicant
- Halperin, John et al., “Safe CGI Programming,” www.improving.org, Sep. 3, 1995, pp. 1-6.Applicant
- “CWSApps Listing (with download) for Incontext WebAnalyzer,” cws.internet.com, Aug. 22, 1996, pp. 1-2.Applicant
- Chi, Ed H. et al., Visualizing the Evolution of Web Ecologies, citeseer,nj.nec.com, 1998, pp. 1-9.Applicant
- Pond, Weld, “L0pht Security Advisory,” www.atstake.com, Dec. 12, 1996, pp. 1-2.Applicant
- Daniels, Tim, “NetCarta's WebMapper: O! What a Tangled Web We Unweave,” www.winnetmag.com, Sep. 1996, pp. 1-6.Applicant
- Strom, David, “Webmapper v 2.0 beta,” www.strom.com, Infoworld, 1997, pp. 1-2, Infoworld Publishing Co.Applicant
- “Urgent Security Announcement,” www.perl.com, Dec. 1995, p. 1.Applicant
- Prymmer, Peter, “Nipert cgi-bin danger,” w4.Ins.comell.edu, Dec. 21, 1996, pp. 1-13.Applicant
- Knorr, Konstantin et al., “Security of Electronic Business Applications: Structure and Quantification, (2000),” citeseer.nj.nec.com, pp. 1-13.Applicant
- Weeks, Judson D. et al., “CCI-Based Web Security: A Design Using PGP,” Fourth International World Wide Web Conference Proceedings, The World Wide Web Journal (www.w3journal.com), Winter 1996, vol. I, Issue 1, pp. 1-24, O'Reilly & Associates.Applicant
- Hammond, Nicolas, “How to Remotely Audit a Secure Web Server,” Presentation to SANS, www.njh.com, Oct. 7, 1999, pp. 1-29.Applicant
- Yang, Ji-Tzay et al., “A Tool Set to Support Web Application Testing,” Proc. of the 1998 International Computer Symposium (ICS), Oct. 1998, pp. 1-8, Department of Computer Science and Information Engineering, National Chiao-Tung University, Taiwan, ROC.Applicant
- McGraw, Gary et al., “Untangling the Woven Web: Testing Web-based Software,” www.rstcorp.com, Apr. 1, 1996, pp. 1-8, Reliable Software Technologies Corporation.Applicant
- Bannan, Karen J., “The InternetUser Guide to 50 Essential Downloads,” PC Magazine, Jun. 1, 1997, pp. 1-18, vol. 16, No. IU.Applicant
- “Internet Security Software Intro'd Aug. 20, 1996,” Newsbytes, pp. 1-3, Information Access Company.Applicant
- “Web server software looks for trouble. Will begin shipping Web Security Scanner, software that lets users check for 100 weak areas,” Network Wold, Aug. 19, 1996, p. 1, Information Access Company.Applicant
- “Buyer's Guide: Web Server Comucopia,” Communications Week, Jun. 2, 1997, p. 1-3, CMP Publications Inc.Applicant
- “Internet Security Systems: Internet Security now shipping network security solutions for Windows NT,” M2 Presswire, Nov. 27, 1996, pp. 1-3, M2 Communications.Applicant
- “SAFEsuite is evaluated the protection of the network,” babelfish.altavista.com, Cetn, Feb. 1997, pp. 66-69.Applicant
- Stoev, Philip, “ELZA.txt,” phiphi.hypemart.net, pp. 1-22.Applicant
- Stoev, Philip, “ELZA 2.txt,” phiphi.hypemart.net, pp. 1-2.Applicant
- “Improving Your Network Security Using SATAN,” www.cs.umbc.edu, Oct. 25, 1995, pp. 1-3.Applicant
- Garfinkel, Simson L., “SATAN Uncovers High Risk of Web Attack: Software Program's Study Details Wide Problems with Security,” www.simson.net, Dec. 19, 1996, pp. 1-3.Applicant
- “Testing Methodology,” www.trouble.org, Dec. 1996, pp. 1-3.Applicant
- “The SATAN Configuration File,” www.procupine.org, Dec. 1996, pp. 1-5.Applicant
- “SATAN Configuration Management,” www.porcupine.org, Dec. 1996, pp. 1-3.Applicant
- “SATAN Rulesets,” www.porcupine.org, Dec. 1996, pp. 1-4.Applicant
- “SATAN Database Format,” www.porcupine.org, Dec. 1996, pp. 1-3.Applicant
- “SiteSweeper 1.0,” LexisNexis, www.nexis.com, Feb. 24, 1997, pp. 1-2, CMP Media Inc.Applicant
- “Internet Probe Droid,” lib.ru/security/ipd.txt, Sep. 29, 1997, pp. 1-15.Applicant