Fixed spelling mistakes.
git-svn-id: http://webgoat.googlecode.com/svn/trunk@64 4033779f-a91e-0410-96ef-6bf7bf53c507
This commit is contained in:
esheri3
parent
3ae171c303
commit
a90d292239
@ -9,8 +9,8 @@ How to Create Database Back Door Attacks.
|
||||
<p>
|
||||
<b>How the attacks works:</b>
|
||||
</p>
|
||||
Database are used usually as a backend for web applications. Also it is used as a media of storage. It can also
|
||||
be used as a place to store a malacious activity such as a trigger. A trigger is called by the database management
|
||||
Databases are used usually as a backend for web applications. Also it is used as a media of storage. It can also
|
||||
be used as a place to store a malicious activity such as a trigger. A trigger is called by the database management
|
||||
system upon the execution of another database operation like insert, select, update or delete. An attacker for example
|
||||
can create a trigger that would set his email address instead of every new user's email address.
|
||||
</div>
|
||||
@ -20,3 +20,4 @@ can create a trigger that would set his email address instead of every new user'
|
||||
* You will not be able to actually create one in this lesson because the underlying database engine used with WebGoat doesn't support triggers.<br>
|
||||
* Your login ID is 101.
|
||||
<!-- Stop Instructions -->
|
||||
|
||||
|
||||
@ -3,7 +3,8 @@
|
||||
</div>
|
||||
<p><b>Concept / Topic To Teach:</b></p>
|
||||
<!-- Start Instructions -->
|
||||
Basic Authentication is used to protect server side resources. The web server will send a 401 authentication request with the response for the requested resource. The client side browser will then prompt the user for a user name and password using a browser supplied dialog box. The browser will base64 encode the user name and password and sendthose credentials back to the web server. The web server will then validate the credentials and return the requested resource if the credentials are correct. These credentials are automatically resent for each page protected with this mechanism without requiring the user to enter their credentials again.<br/>
|
||||
Basic Authentication is used to protect server side resources. The web server will send a 401 authentication request with the response for the requested resource. The client side browser will then prompt the user for a user name and password using a browser supplied dialog box. The browser will base64 encode the user name and password and send those credentials back to the web server. The web server will then validate the credentials and return the requested resource if the credentials are correct. These credentials are automatically resent for each page protected with this mechanism without requiring the user to enter their credentials again.<br/>
|
||||
<p><b>General Goal(s):</b></p>
|
||||
For this lesson, your goal is to understand Basic Authentication and answer the questions below.
|
||||
<!-- Stop Instructions -->
|
||||
|
||||
|
||||
@ -8,8 +8,8 @@ SQL injection attacks represent a serious threat to any database-driven site. Th
|
||||
<br>
|
||||
Not only is it a threat easily instigated, it is also a threat that, with a little common-sense and forethought, can be almost totally prevented. This lesson will show the student several examples of SQL injection.<br>
|
||||
<br>
|
||||
It is always good practice to sanitize all input data, especially data that will used in OS command, scripts, and database queiries.<br>
|
||||
It is always good practice to sanitize all input data, especially data that will used in OS command, scripts, and database queries.<br>
|
||||
<!-- Stop Instructions -->
|
||||
|
||||
<p><b>General Goal(s):</b> </p>
|
||||
The form below allows a user to enter an account number and determine if it is valid or not. Use this form to develop a true / false test check other entries in the database.<br><br>Reference Ascii Values: 'A' = 65 'Z' = 90 'a' = 97 'z' = 122<br><br>The goal is to find the value of the first_name in table user_data for userid 15613. Put that name in the form to pass the lesson.
|
||||
The form below allows a user to enter an account number and determine if it is valid or not. Use this form to develop a true / false test check other entries in the database.<br><br>Reference Ascii Values: 'A' = 65 'Z' = 90 'a' = 97 'z' = 122<br><br>The goal is to find the value of the first_name in table user_data for userid 15613. Put that name in the form to pass the lesson.
|
||||
|
||||
@ -21,5 +21,6 @@ In this way, the attacker can make the victim perform actions that they didn't i
|
||||
</div>
|
||||
<p><b>General Goal(s):</b> </p>
|
||||
<!-- Start Instructions -->
|
||||
Your goal is to send an email to a newsgroup that contains an image whose URL is pointing to a malacious request. Try to include a 1x1 pixel image that includes a URL. The URL should point to the CSRF lesson with an extra parameter "transferFunds=4000". You can copy the shortcut from the left hand menu, right click on the left hand menu and choose copy shortcut. Whoever receives this email and happens to be authenticated at that time will have his funds transfered. When you think the attack is successfull, refresh the page and you will find the green check on the left hand side menu.
|
||||
Your goal is to send an email to a newsgroup that contains an image whose URL is pointing to a malicious request. Try to include a 1x1 pixel image that includes a URL. The URL should point to the CSRF lesson with an extra parameter "transferFunds=4000". You can copy the shortcut from the left hand menu, right click on the left hand menu and choose copy shortcut. Whoever receives this email and happens to be authenticated at that time will have his funds transferred. When you think the attack is successful, refresh the page and you will find the green check on the left hand side menu.
|
||||
<!-- Stop Instructions -->
|
||||
|
||||
|
||||
@ -3,9 +3,10 @@
|
||||
</div>
|
||||
<p><b>Concept / Topic To Teach:</b></p>
|
||||
<!-- Start Instructions -->
|
||||
It is always a good practice to scrub all inputs, especially those inputs that will later be used as parameters to OS commands, scripts, and database queries. It is particularly important for content that will be permanently stored somewhere. Users should not be able to create message content that could cause another user to load an undesireable page or undesireable content when the user's message is retrieved.<br>
|
||||
It is always a good practice to scrub all inputs, especially those inputs that will later be used as parameters to OS commands, scripts, and database queries. It is particularly important for content that will be permanently stored somewhere. Users should not be able to create message content that could cause another user to load an undesirable page or undesirable content when the user's message is retrieved.<br>
|
||||
XSS can also occur when unvalidated user input is used in an HTTP response. In a reflected XSS attack, an attacker can craft a URL with the attack script and post it to another website, email it, or otherwise get a victim to click on it.
|
||||
<!-- Stop Instructions -->
|
||||
<p><b>General Goal(s):</b></p>
|
||||
For this exercise, you will perform stored and reflected XSS attacks. You will also implement code changes in the web application to defeat these attacks.
|
||||
<br>
|
||||
|
||||
|
||||
@ -16,7 +16,8 @@ javascript commands to exploit his attacks.
|
||||
</div>
|
||||
<p><b>General Goal(s):</b> </p>
|
||||
<!-- Start Instructions -->
|
||||
* Your victim is a system that takes an activatation key to allow you to use it.<br>
|
||||
* Your victim is a system that takes an activation key to allow you to use it.<br>
|
||||
* Your goal should be to try to get to enable the activate button.<br>
|
||||
* Take some time to see the HTML source in order to understand how the key validation process works.<br>
|
||||
<!-- Stop Instructions -->
|
||||
|
||||
|
||||
@ -3,7 +3,7 @@
|
||||
</div>
|
||||
<p><b>Concept / Topic To Teach:</b> </p>
|
||||
<!-- Start Instructions -->
|
||||
Developers will use hidden fields for tracking, login, pricing, etc.. information on a loaded page. While this is a convienent and easy mechanism for the developer, they often don't validate the information that is received from the hidden field. This lesson will teach the attacker to find and modify hidden fields to obtain a product for a price other than the price specified <br>
|
||||
Developers will use hidden fields for tracking, login, pricing, etc.. information on a loaded page. While this is a convenient and easy mechanism for the developer, they often don't validate the information that is received from the hidden field. This lesson will teach the attacker to find and modify hidden fields to obtain a product for a price other than the price specified <br>
|
||||
<!-- Stop Instructions -->
|
||||
<p><b>General Goal(s):</b> </p>
|
||||
The user should be able to exploit a hidden field to obtain a product at an incorrect price.
|
||||
The user should be able to exploit a hidden field to obtain a product at an incorrect price.
|
||||
|
||||
@ -4,8 +4,8 @@
|
||||
|
||||
<p><b>Concept / Topic To Teach:</b> </p>
|
||||
<!-- Start Instructions -->
|
||||
Developers are notorious for leaving statements like FIXME's, Code Broken, Hack, etc... inside the source code. Review the source code for any comments denoting passowrds, backdoors, or something doesn't work right.
|
||||
Developers are notorious for leaving statements like FIXME's, Code Broken, Hack, etc... inside the source code. Review the source code for any comments denoting passwords, backdoors, or something doesn't work right.
|
||||
<!-- Stop Instructions -->
|
||||
<br>
|
||||
<p><b>General Goal(s):</b> </p>
|
||||
The user should be able to bypass the authentication check.
|
||||
The user should be able to bypass the authentication check.
|
||||
|
||||
@ -11,13 +11,14 @@ This lesson teaches how to perform JSON Injection Attacks.
|
||||
</p>
|
||||
JavaScript Object Notation (JSON) is a simple and effective lightweight data exchange format. JSON can be in a lot of forms such as arrays, lists, hashtables and other data structures.
|
||||
JSON is widely used in AJAX and Web2.0 application and is favored by programmers over XML because of its ease of use and speed.
|
||||
However, JSON, like XML is prone to Injection attacks. A malacious attackers can inject the reply from the server and inject some aribtrary values in there.
|
||||
However, JSON, like XML is prone to Injection attacks. A malicious attacker can inject the reply from the server and inject some arbitrary values in there.
|
||||
|
||||
</div>
|
||||
<p><b>General Goal(s):</b> </p>
|
||||
<!-- Start Instructions -->
|
||||
* You are travelling from Boston, MA- Airport code BOS to Seattle, WA - Airport code SEA.<br>
|
||||
* You are traveling from Boston, MA- Airport code BOS to Seattle, WA - Airport code SEA.<br>
|
||||
* Once you enter the three digits code of the airport, an AJAX request will be executed asking for the tickets price.<br>
|
||||
* You will notice that there are two flights available, an expensive one with no stops and another cheaper one with 2 stops.<br>
|
||||
* Your goal is to try to get the one with no stops but for a cheaper price.
|
||||
<!-- Stop Instructions -->
|
||||
|
||||
|
||||
@ -3,8 +3,8 @@
|
||||
</div>
|
||||
<p><b>Concept / Topic To Teach:</b> </p>
|
||||
<!-- Start Instructions -->
|
||||
Client-side validation should not be considered a secure means of validating parameters. These validation only help reduce the amount of server processing time for normal users who do not know the format of required input. Attackers can bypass these mechanisms easily in various ways. Any client-side validation should be duplicated on the server side. This will greatly reduce the likelyhood of insecure parameter values being used in the application.
|
||||
Client-side validation should not be considered a secure means of validating parameters. These validations only help reduce the amount of server processing time for normal users who do not know the format of required input. Attackers can bypass these mechanisms easily in various ways. Any client-side validation should be duplicated on the server side. This will greatly reduce the likelihood of insecure parameter values being used in the application.
|
||||
<!-- Stop Instructions -->
|
||||
<br>
|
||||
<p><b>General Goal(s):</b> </p>
|
||||
For this exercise, the web site requires that you follow certain rules when you fill out a form. The user should be able to break those rules, and send the website input that it wasn't expecting. <br>
|
||||
For this exercise, the web site requires that you follow certain rules when you fill out a form. The user should be able to break those rules, and send the website input that it wasn't expecting. <br>
|
||||
|
||||
@ -2,10 +2,10 @@
|
||||
<p><b>Lesson Plan Title: </b>How to Force Browser Web Resources</p>
|
||||
</div>
|
||||
<p><b>Concept / Topic To Teach:</b> </p>
|
||||
Applications will often have an adminstrative interface that allows privileged users access to functionality that normal users shouldn't see. The application server will often have an admin interface as well.
|
||||
<p><b>Standards Addressed:</b> </p>
|
||||
Applications will often have an administrative interface that allows privileged users access to functionality that normal users shouldn't see. The application server will often have an admin interface as well.
|
||||
<p><b>Standards Addressed :</b> </p>
|
||||
<p><b>General Goal(s):</b>
|
||||
<!-- Start Instructions -->
|
||||
Try to access the administrative interface for WebGoat. You may also try to access the administrative interface for Tomcat. The Tomcat admin interface can be accessed via a URL (/admin) and will not count towards the completion of this lesson.
|
||||
<!-- Stop Instructions -->
|
||||
</p>
|
||||
</p>
|
||||
|
||||
@ -8,7 +8,7 @@ SQL injection attacks represent a serious threat to any database-driven site. Th
|
||||
<br>
|
||||
Not only is it a threat easily instigated, it is also a threat that, with a little common-sense and forethought, can be almost totally prevented. This lesson will show the student several examples of SQL injection.<br>
|
||||
<br>
|
||||
It is always good practice to sanitize all input data, especially data that will used in OS command, scripts, and database queiries.<br>
|
||||
It is always good practice to sanitize all input data, especially data that will used in OS command, scripts, and database queries.<br>
|
||||
<p><b>General Goal(s):</b> </p>
|
||||
The form below allows a user to view weather data. Try to inject an SQL string that results in all the weather data being displayed.
|
||||
<!-- Stop Instructions -->
|
||||
<!-- Stop Instructions -->
|
||||
|
||||
@ -8,7 +8,7 @@ SQL injection attacks represent a serious threat to any database-driven site. Th
|
||||
<br>
|
||||
Not only is it a threat easily instigated, it is also a threat that, with a little common-sense and forethought, can be almost totally prevented. This lesson will show the student several examples of SQL injection.<br>
|
||||
<br>
|
||||
It is always good practice to sanitize all input data, especially data that will used in OS command, scripts, and database queiries.<br>
|
||||
It is always good practice to sanitize all input data, especially data that will used in OS command, scripts, and database queries.<br>
|
||||
<p><b>General Goal(s):</b> </p>
|
||||
The form below allows a user to view their credit card numbers. Try to inject an SQL string that results in all the credit card numbers being displayed. Try the user name of 'Smith'.
|
||||
<!-- Stop Instructions -->
|
||||
<!-- Stop Instructions -->
|
||||
|
||||
@ -3,7 +3,7 @@
|
||||
</div>
|
||||
<p><b>Concept / Topic To Teach:</b> </p>
|
||||
<!-- Start Instructions -->
|
||||
It is always a good practice to scrub all inputs, especially those inputs that will later be used as parameters to OS commands, scripts, and database queries. It is particularly important for content that will be permanently stored somewhere. Users should not be able to create message content that could cause another user to load an undesireable page or undesireable content when the user's message is retrieved.
|
||||
It is always a good practice to scrub all inputs, especially those inputs that will later be used as parameters to OS commands, scripts, and database queries. It is particularly important for content that will be permanently stored somewhere. Users should not be able to create message content that could cause another user to load an undesirable page or undesirable content when the user's message is retrieved.
|
||||
<!-- Stop Instructions -->
|
||||
<p><b>General Goal(s):</b> </p>
|
||||
The user should be able to add message content that cause another user to load an undesireable page or content.
|
||||
The user should be able to add message content that cause another user to load an undesirable page or content.
|
||||
|
||||
@ -3,7 +3,7 @@
|
||||
</div>
|
||||
<p><b>Concept / Topic To Teach:</b> </p>
|
||||
<!-- Start Instructions -->
|
||||
It is always a good practice to scrub all inputs, especially those inputs that will later be used as parameters to OS commands, scripts, and database queries. It is particularly important for content that will be permanently stored somewhere. Users should not be able to create message content that could cause another user to load an undesireable page or undesireable content when the user's message is retrieved.
|
||||
It is always a good practice to scrub all inputs, especially those inputs that will later be used as parameters to OS commands, scripts, and database queries. It is particularly important for content that will be permanently stored somewhere. Users should not be able to create message content that could cause another user to load an undesirable page or undesirable content when the user's message is retrieved.
|
||||
<p><b>General Goal(s):</b> </p>
|
||||
Tomcat is configured to support the HTTP TRACE command. Your goal is to perform a Cross Site Trace (XST) attack.
|
||||
<!-- Stop Instructions -->
|
||||
<!-- Stop Instructions -->
|
||||
|
||||
@ -3,7 +3,7 @@
|
||||
</div>
|
||||
<p><b>Concept / Topic To Teach:</b> </p>
|
||||
<!-- Start Instructions -->
|
||||
It is always a good practice to validate all inputs. Most sites allow a non-authenticated users to send email to a 'friend'. This is a great mechanisms for spammers to send out email using your corporate mail server.
|
||||
It is always a good practice to validate all inputs. Most sites allow non-authenticated users to send email to a 'friend'. This is a great mechanism for spammers to send out email using your corporate mail server.
|
||||
<!-- Stop Instructions -->
|
||||
<p><b>General Goal(s):</b> </p>
|
||||
The user should be able to send and obnoxious email message.
|
||||
The user should be able to send and obnoxious email message.
|
||||
|
||||
@ -4,7 +4,7 @@
|
||||
|
||||
<p><b>Concept / Topic To Teach:</b> </p>
|
||||
<!-- Start Instructions -->
|
||||
Many applications will automatically log a user into their site if the right authentication cookie is specified. Some times the cookie values can be guessed if the algorithm for generating the cookie can be obtained. Some times the cookies are left on the client machine and can be stolen by exploiting another system vulnerability. Some times the cookies maybe intercepted using Ccross site scripting. This lesson tries to make the student aware of authentication cookies and presents the student with a way to defeat the cookie authentication method in this lesson.<br>
|
||||
Many applications will automatically log a user into their site if the right authentication cookie is specified. Some times the cookie values can be guessed if the algorithm for generating the cookie can be obtained. Some times the cookies are left on the client machine and can be stolen by exploiting another system vulnerability. Some times the cookies maybe intercepted using Cross site scripting. This lesson tries to make the student aware of authentication cookies and presents the student with a way to defeat the cookie authentication method in this lesson.<br>
|
||||
<!-- Stop Instructions -->
|
||||
<p><b>General Goal(s):</b> </p>
|
||||
The user should be able to bypass the authentication check.
|
||||
The user should be able to bypass the authentication check.
|
||||
|
||||
@ -5,5 +5,5 @@
|
||||
<!-- Start Instructions -->
|
||||
Web Services communicate through the use of SOAP requests. These requests are submitted to a web service in an attempt to execute a function listed in the web service definition language (WSDL).
|
||||
<p><b>General Goal(s):</b> </p>
|
||||
Some web interfaces make use of Web Services in the background. If the frontend relies on the web service for all input validation, it may be possible to corrupt the XML that the web interface sends.<br/>In this exercise, try to change the password for a user other than 101.
|
||||
<!-- Stop Instructions -->
|
||||
Some web interfaces make use of Web Services in the background. If the front-end relies on the web service for all input validation, it may be possible to corrupt the XML that the web interface sends.<br/>In this exercise, try to change the password for a user other than 101.
|
||||
<!-- Stop Instructions -->
|
||||
|
||||
@ -5,5 +5,5 @@
|
||||
<!-- Start Instructions -->
|
||||
Web Services communicate through the use of SOAP requests. These requests are submitted to a web service in an attempt to execute a function listed in the web service definition language (WSDL).
|
||||
<p><b>General Goal(s):</b> </p>
|
||||
Check the web service description language (WSDL) and try to obtain multiple customer credit card numbers. You will not see the results returned to this screen. When you believe you have suceeded, refresh the page and look for the 'green star'
|
||||
<!-- Stop Instructions -->
|
||||
Check the web service description language (WSDL) and try to obtain multiple customers credit card numbers. You will not see the results returned to this screen. When you believe you have succeeded, refresh the page and look for the 'green star'
|
||||
<!-- Stop Instructions -->
|
||||
|
||||
@ -9,10 +9,11 @@
|
||||
<p>
|
||||
<b>How the attacks works:</b>
|
||||
</p>
|
||||
AJAX applications use XML to exchange information with the server. This XML can be easily intercepted and altered by a malacious attacker.
|
||||
AJAX applications use XML to exchange information with the server. This XML can be easily intercepted and altered by a malicious attacker.
|
||||
|
||||
</div>
|
||||
<p><b>General Goal(s):</b> </p>
|
||||
<!-- Start Instructions -->
|
||||
WebGoat-Miles Reward Miles shows all the rewards available. Once, you enter your account ID, it will show you your balance and the ones that you can afford. Your goal is to try to add more rewards to your allowed set of rewards. Your account ID is 836239.
|
||||
WebGoat-Miles Reward Miles shows all the rewards available. Once you’ve entered your account ID, the lesson will show you your balance and the products you can afford. Your goal is to try to add more rewards to your allowed set of rewards. Your account ID is 836239.
|
||||
<!-- Stop Instructions -->
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user