Test Local Storage (OTG-CLIENT-012) - Revision history

Nvhaver: /Test Local Storage/

2014-12-01T19:08:58Z

‎Test Local Storage

Andrew Muller at 13:46, 8 August 2014

2014-08-08T13:46:09Z

Andrew Muller: Andrew Muller moved page Test Local Storage (OTG-CLIENT-007) to Test Local Storage (OTG-CLIENT-012)

2014-08-05T12:15:25Z

Andrew Muller moved page Test Local Storage (OTG-CLIENT-007) to Test Local Storage (OTG-CLIENT-012)

Jane O'Connor: Final edit

2014-05-19T12:38:01Z

Final edit

Jgaliana: added ZAP Proxy

2013-12-15T18:52:54Z

added ZAP Proxy

Jgaliana: minor formating change in references section

2013-12-15T18:50:44Z

minor formating change in references section

Jgaliana: minor additions/changes

2013-12-15T18:50:03Z

minor additions/changes

Jgaliana: changed black box/gray box testing and example

2013-12-15T17:39:25Z

changed black box/gray box testing and example

Jgaliana: link added

2013-12-14T23:59:26Z

link added

Jgaliana: adding OWASP Testing Guide v4 template

2013-12-14T23:32:52Z

adding OWASP Testing Guide v4 template

@@ Line 20: / Line 20: @@
 === sessionStorage ===
-Main difference with localStorage is that the data stored in this object is only accessible until the tab/window is closed which is a perfect candidate for data that doesn't need to persist between sessions. It shares most of the properties and the getItem/setItem methods, so manual testing needs to be undertaken to look for these methods and identify in which parts of the code the storage is accessed.
+The main difference with localStorage is that the data stored in this object is only accessible until the tab/window is closed, which makes localStorage a perfect candidate for data that doesn't need to be persisted between sessions. It shares most of the properties and the getItem/setItem methods, so manual testing needs to be undertaken to look for these methods and identify in which parts of the code the storage is accessed.
 ==How to Test==
@@ Line 58: / Line 58: @@
-Next manual testing needs to be conducted in order to determine whether the website is storing sensitive data in the storage that represents a risk and will increase dramatically the impact of a information leak. Also check the code handling the Storage to determine if it is vulnerable to injection attacks, common issue when the code does not escape the input or output. The JavaScript code has to be analyzed to evaluate these issues, so make sure you crawl the application to discover every instance of JavaScript code and note sometimes applications use third-party libraries that would need to be examined too.<br>
+Next manual testing needs to be conducted in order to determine whether the website is storing sensitive data in the storage that represents a risk and will increase dramatically the impact of an information leak. Also check the code handling the Storage to determine if it is vulnerable to injection attacks, common issue when the code does not escape the input or output. The JavaScript code has to be analyzed to evaluate these issues, so make sure you crawl the application to discover every instance of JavaScript code and note sometimes applications use third-party libraries that would need to be examined too.<br>
 <br>
 Here is an example of how improper use of user input and lack of validation can lead to XSS attacks.

@@ Line 2: / Line 2: @@
-== Brief Summary ==
+== Summary ==
 Local Storage also known as Web Storage or Offline Storage is a mechanism to store data as key/value pairs tied to a domain and enforced by the same origin policy (SOP). There are two objects, localStorage that is persistent and is intended to survive browser/system reboots and sessionStorage that is temporary and will only exists until the window or tab is closed.
@@ Line 10: / Line 10: @@
 === localStorage ===
@@ Line 23: / Line 22: @@
 Main difference with localStorage is that the data stored in this object is only accessible until the tab/window is closed which is a perfect candidate for data that doesn't need to persist between sessions. It shares most of the properties and the getItem/setItem methods, so manual testing needs to be undertaken to look for these methods and identify in which parts of the code the storage is accessed.
+==How to Test==
-== Black Box testing and example ==
+=== Black Box testing ===
 Black box testing for issues within the Local Storage code is not usually performed since access to the source code is always available as it needs to be sent to the client to be executed.
-== Gray Box testing and example ==
+=== Gray Box testing ===
 First of all, we need to check whether the Local Storage is used.
@@ Line 90: / Line 89: @@
 [[File:Storage-xss.png]]
 == References ==
@@ Line 99: / Line 104: @@
 '''Whitepapers'''
 *'''Web Storage Specification''': http://www.w3.org/TR/webstorage/

@@ Line 4: / Line 4: @@
 == Brief Summary ==
-Local Storage also known as Web Storage or Offline Storage is a mechanism to store data as key/value pairs tied to a domain and enforced by the same origin policy (SOP).
+Local Storage also known as Web Storage or Offline Storage is a mechanism to store data as key/value pairs tied to a domain and enforced by the same origin policy (SOP). There are two objects, localStorage that is persistent and is intended to survive browser/system reboots and sessionStorage that is temporary and will only exists until the window or tab is closed.
-There are two objects, localStorage that is persistent and is intented to survive browser/system reboots and sessionStorage that is temporary and will only exists until the window or tab is closed. On average browsers allow to store in this storage around 5MB per domain, that compared to the 4KB of cookies is a big difference, but the key difference from the security perspective is that the data stored in these two objects is kept in the client and never sent to the server, this also improves network performance as data do not need to travel over the wire back and forth.
 == Description of the Issue ==
 === localStorage ===
-Access to the storage is normally done using the setItem and getItem functions. The storage can be read from javascript which means with a single XSS an attacker would be able to extract all the data from the storage.
+Access to the storage is normally done using the setItem and getItem functions. The storage can be read from javascript which means with a single XSS an attacker would be able to extract all the data from the storage. Also malicious data can be loaded into the storage via JavaScript so the application needs to have the controls in place to treat untrusted data. Check if there are more than one application in the same domain like example.foo/app1 and example.foo/app2 because those will share the  same  storage.
 Also malicious data can be loaded into the storage via JavaScript so the application needs to have the controls in place to treat untrusted data.
 Data stored in this object will persist after the window is closed, it is a bad idea to store sensitive data or session identifiers on this object as these can be accesed via JavaScript. Session IDs stored in cookies can mitigate this risk using the httpOnly flag.
@@ Line 19: / Line 21: @@
 === sessionStorage ===
-Main difference with localStorage is that the data stored in this object is only accesible until the tab/window is closed which is a perfect candidate for data that doesn't need to persist between sessions.
+Main difference with localStorage is that the data stored in this object is only accessible until the tab/window is closed which is a perfect candidate for data that doesn't need to persist between sessions. It shares most of the properties and the getItem/setItem methods, so manual testing needs to be undertaken to look for these methods and identify in which parts of the code the storage is accessed.
 == Gray Box testing and example ==
@@ Line 33: / Line 34: @@
 '''Example 1: Access to localStorage:''' <br>
-<br>
 Access to every element in localStorage with JavaScript:<br>
@@ Line 45: / Line 46: @@
-Using Google Chrome, click on menu -> Tools -> Developer Tools. Then under Resources you will see 'Local Storage' and 'Web Storage'
+Using Google Chrome, click on menu -> Tools -> Developer Tools. Then under Resources you will see 'Local Storage' and 'Web Storage'.
 [[File:storage-chrome.png]]
-Using Firefox and the addon Firebug you can easily inspect the localStorage/sessionStorage object in the DOM tab
+Using Firefox with the Firebug add on you can easily inspect the localStorage/sessionStorage object in the DOM tab.
 [[File:storage-firefox.png]]
@@ Line 58: / Line 59: @@
-Then, manual testing needs to be conducted in order to determine whether the website is storing sensitive data in the Storage, which respresent a risk and will increase dramatically the impact of a information leak. Also check the code handling the Storage to determine if it is vulnerable to injection attacks, common issue when the code does not escape the input or output. The JavaScript code has to be analyzed to evaluate these issues, so make sure you crawl the application to discover every instance of JavaScript code and note sometimes applications use third-party libraries that would need to be examined too.<br>
+Next manual testing needs to be conducted in order to determine whether the website is storing sensitive data in the storage that represents a risk and will increase dramatically the impact of a information leak. Also check the code handling the Storage to determine if it is vulnerable to injection attacks, common issue when the code does not escape the input or output. The JavaScript code has to be analyzed to evaluate these issues, so make sure you crawl the application to discover every instance of JavaScript code and note sometimes applications use third-party libraries that would need to be examined too.<br>
 <br>
 Here is an example of how improper use of user input and lack of validation can lead to XSS attacks.
 Insecure assignment from localStorage can lead to XSS<br>
@@ Line 86: / Line 86: @@
 URL PoC:
-http://server/StoragePOC.html#<img src=x onerror=alert(1)>
+ http://server/StoragePOC.html#<img src=x onerror=alert(1)>
 [[File:Storage-xss.png]]
@@ Line 95: / Line 95: @@
 '''OWASP Resources'''
 *'''OWASP HTML5 Security Cheat Sheet''': https://www.owasp.org/index.php/HTML5_Security_Cheat_Sheet
 '''Whitepapers'''
 *'''Web Storage Specification''': http://www.w3.org/TR/webstorage/
 '''Tools'''

← Older revision		Revision as of 18:52, 15 December 2013
Line 102:		Line 102:
	* '''Firebug''' - http://getfirebug.com/		* '''Firebug''' - http://getfirebug.com/
	* '''Google Chrome Developer Tools''' - https://developers.google.com/chrome-developer-tools/		* '''Google Chrome Developer Tools''' - https://developers.google.com/chrome-developer-tools/
		+	* '''OWASP Zed Attack Proxy (ZAP)''' - https://www.owasp.org/index.php/OWASP_Zed_Attack_Proxy_Project
		+	ZAP is an easy to use integrated penetration testing tool for finding vulnerabilities in web applications. It is designed to be used by people with a wide range of security experience and as such is ideal for developers and functional testers who are new to penetration testing. ZAP provides automated scanners as well as a set of tools that allow you to find security vulnerabilities manually.

@@ Line 99: / Line 99: @@
 *'''Web Storage Specification''': http://www.w3.org/TR/webstorage/
+'''Tools'''
 * '''Firebug''' -  http://getfirebug.com/
 * '''Google Chrome Developer Tools''' - https://developers.google.com/chrome-developer-tools/

← Older revision	Revision as of 12:15, 5 August 2014
(No difference)

← Older revision		Revision as of 23:32, 14 December 2013
Line 1:		Line 1:
		+	{{Template:OWASP Testing Guide v4}}
		+
		+
	== Brief Summary ==		== Brief Summary ==