[Owasp-o2-platform] Fwd: O2 Platform support for WebGoat

dinis cruz dinis.cruz at owasp.org
Tue Jun 29 07:38:17 EDT 2010

I just sent the email below to the OWASP's WebGoat community and I think it
is a good example of the type of integration (and value) that O2 should
provide with other OWASP projects.

If you are into BlackBox testing, check out the Web Automation example since
you should be using that technique today in your engagements :)


---------- Forwarded message ----------
From: dinis cruz <dinis.cruz at owasp.org>
Date: 29 June 2010 12:31
Subject: O2 Platform support for WebGoat
To: owasp-webgoat at lists.owasp.org

Hi WebGoat Crowd

I finally started adding support for WebGoat to the OWASP O2
Platform<http://www.owasp.org/index.php/OWASP_O2_Platform> by
creating an API for Web Goat and showing how to automate a number of
WebGoat's tasks and lessons. I've started to documentat how to use it and
how it works, which you can read it (or watch the video) here:

At the moment there is a first pass at an API for WebGoat (see
API_WebGoat.cs) and a number of Unit Tests (see WebGoat_BlackBox_Exploits.cs).
Both these files are available locally when you install the O2
the WebGoat_BlackBox_Exploits.cs can be executed by double-clicking on it or
dragging'n'dropping it into a loaded O2 instance (see video for an example)

So far the following browser-driven UnitTests/WebAutomation workflows have
been implemented:

   - Download the latest version of WebGoat (starting in the OWASP website
   and ending with the download 'save as' pop-up from Google Code)
   - Start a local copy of WebGoat
   - Open the WebGoat HomePage (with support for auto submitting the
   WebGoat's Basic Auth requirement (using guest:guest), and clicking on the
   'Start WebGoat' button)
   - Complete the Lab: "Cross-Site Scripting (XSS) --> LAB: Cross Site
   Scripting --> Stage 1: Stored XSS " using two injection points: the
   "address1" field (which is vulnerable to XSS) and the "description" field
   (which is NOT vulnerable to XSS)

The Stored XSS lesson is a good example of O2's powerful web automation
capabilities (using WatiN's engine on top of IE) since it shows how complex
web workflows can be easily created, tested and packaged:

    	    	public string Exploit_Stage_1_Stored_XSS_OK()
    	     		return Exploit_Stage_1_Stored_XSS("address1");

		public string Exploit_Stage_1_Stored_XSS_Fail()
			return Exploit_Stage_1_Stored_XSS("description");
		private string Exploit_Stage_1_Stored_XSS(string fieldToInsertPayload)
			var payload = "<a href=\"\"
onMouseOver=\"javascript:alert('xss')\">Over me to see xss</a>";
			ie.link("Cross-Site Scripting (XSS)").flash().click();
			ie.link("LAB: Cross Site Scripting").flash().click();			
			ie.link("Stage 1: Stored XSS").flash();
"Payload was not inserted into page");
			return "ok";

The sample code above (from WebGoat_BlackBox_Exploits.cs is designed to be
easy to read and write/test (using one of O2's
development/test environments).

For example:

	*ie.link("LAB: Cross Site Scripting").flash().click();*


   - in the current page, find the link called "Lab: Cross Site Scripting"
   - flash the link 3 times (i.e. scroll the browser to the current
page location of the link (which could be outside the user's view) and
set its background color to yellow for a couple seconds)
   - click on the link
   - wait for the linked page to load completely before continuing execution



   - find the field called "password" in the current page
   - flash it 3 times
   - set the value of the field to "larry"



   - get a list of 'Selection Lists' from the current page (these are
also called DropDownList/ComboBox)
   - select the 2nd SelectionList (we couldn't get the reference using
the name since its HtmlElement didn't seem to have a value that could
be used to find it)
   - get the current Options of the chosen SelectionList (this is the
list of the DropDownList options/values)
   - chose the first option and selected it
   - Flash the selected option so the user can see which one we chose

Hopefully this all makes sense, and you (webGoat community) can now
continue this from here.

Ideally we should have all WebGoat Lessons mapped using these Security
UnitTests, and once that is done, create a 'secure version of WebGoat'
that passes all those UnitTests (assuming the UnitTests are designed
to succeed when the vulnerability was exploited)

Please have a go and let me know if you have any problems or ideas on
how to improve it (see the video on
http://o2platform.com/wiki/WebGoat/First_Example_of_O2_WebGoat_API if
you have questions on how to use the WebGoat_BlackBox_Exploits.cs

Dinis Cruz

Blog: http://diniscruz.blogspot.com
Twitter: http://twitter.com/DinisCruz
Web: http://www.owasp.org/index.php/O2
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.owasp.org/pipermail/owasp-o2-platform/attachments/20100629/e03f1ab7/attachment.html 

More information about the Owasp-o2-platform mailing list