This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "Testing for Session Management"
m (proofreading) |
(→4.5 Session Management Testing) |
||
| Line 19: | Line 19: | ||
Session Tokens represent confidential informations because they tie the user identity with his own session. It's possible to test if the session token is exposed to this vulnerability and try to create a replay session attack. | Session Tokens represent confidential informations because they tie the user identity with his own session. It's possible to test if the session token is exposed to this vulnerability and try to create a replay session attack. | ||
<br> | <br> | ||
| − | [[ | + | [[ Testing for CSRF|4.5.4 Cross Site Request Forgery (CSRF) ]]<br> |
| − | + | CSRF describes a way to force an unknowing user to execute unwanted actions on a web application in which he is currently authenticated.<br> | |
[[ HTTP Exploit AoC|4.5.5 HTTP Exploit ]]<br> | [[ HTTP Exploit AoC|4.5.5 HTTP Exploit ]]<br> | ||
Here is described how to test for an HTTP Exploit.<br><br> | Here is described how to test for an HTTP Exploit.<br><br> | ||
Revision as of 00:33, 19 January 2007
[Up]
OWASP Testing Guide v2 Table of Contents
4.5 Session Management Testing
At the core of any web-based application is the way in which it maintains state and thereby controls user-interaction with the site. Session Management broadly covers all controls on a user from authentication to leaving the application.
HTTP is a stateless protocol, meaning web servers respond to client requests without linking them to each other. Even simple application logic requires a user's multiple requests to be associated with each other across a "session”. This necessitates third party solutions – through either Off-The-Shelf (OTS) middleware and web server solutions, or bespoke developer implementations. Most popular web application environments, such as ASP and PHP, provide developers with built in session handling routines. Some kind of identification token will typically be issued, which will be referred to as a “Session ID” or Cookie.
There are a number of ways a web application may interact with a user. Each is dependent upon the nature of the site, the security and availability requirements of the application.
Whilst there are accepted best practices for application development, such as those outlined in the OWASP Guide to Building Secure Web Applications, it is important that application security is considered within the context of the provider’s requirements and expectations. In this chapter we describe the following items.
4.5.1 Analysis of the Session Management Schema
This paragraph describes how to analyse a Session Management Schema, with the goal to understand how the Session Management mechanism has been developed and if it is possible to break it
4.5.2 Cookie and Session Token Manipulation
Here it is explained how to test the security of session Token issued to the Client: how to make a cookie reverse engineering, and a cookie manipulation to force an hijacked session to work
4.5.3 Exposed Session Variables
Session Tokens represent confidential informations because they tie the user identity with his own session. It's possible to test if the session token is exposed to this vulnerability and try to create a replay session attack.
4.5.4 Cross Site Request Forgery (CSRF)
CSRF describes a way to force an unknowing user to execute unwanted actions on a web application in which he is currently authenticated.
4.5.5 HTTP Exploit
Here is described how to test for an HTTP Exploit.
OWASP Testing Guide v2
Here is the OWASP Testing Guide v2 Table of Contents
