Difference between revisions of "Top 10 2010-A3-Broken Authentication and Session Management"

From OWASP
Jump to: navigation, search
Line 1: Line 1:
 
{{Top_10_2010:TopTemplate|usenext=NextLink|next=-Broken Authentication and Session Management|useprev=PrevLink|prev=-Cross Site Request Forgery|usemain=MainLink|main=}}  
 
{{Top_10_2010:TopTemplate|usenext=NextLink|next=-Broken Authentication and Session Management|useprev=PrevLink|prev=-Cross Site Request Forgery|usemain=MainLink|main=}}  
 +
 +
 +
[[http://www.owasp.org/index.php/ASVS#tab=Download|ASVS]]
  
 
<center>
 
<center>
Line 36: Line 39:
 
#Are passwords, session IDs, and other credentials sent only over TLS connections? See A9.
 
#Are passwords, session IDs, and other credentials sent only over TLS connections? See A9.
  
See the [[http://www.owasp.org/index.php/ASVS#tab=Download ASVS]] requirement areas V2 and V3 for more details.
+
See the [[http://www.owasp.org/index.php/ASVS|ASVS]] requirement areas V2 and V3 for more details.
 
}}
 
}}
  
Line 42: Line 45:
 
The primary recommendation for an organization is to make available to developers:
 
The primary recommendation for an organization is to make available to developers:
 
# '''A single set of strong authentication and session management controls'''. Such controls should strive to:
 
# '''A single set of strong authentication and session management controls'''. Such controls should strive to:
## meet all the authentication and session management requirements defined in OWASP’s [[http://www.owasp.org/index.php/ASVS#tab=Download Application Security Verification Standard]] (ASVS) areas V2 (Authentication) and V3 (Session Management).
+
## meet all the authentication and session management requirements defined in OWASP’s [http://www.owasp.org/index.php/ASVS#tab=Download Application Security Verification Standard] (ASVS) areas V2 (Authentication) and V3 (Session Management).
## have a simple interface for developers. Consider the [[http://owasp-esapi-java.googlecode.com/svn/trunk_doc/latest/org/owasp/esapi/Authenticator.html ESAPI Authenticator and User APIs]]
+
## have a simple interface for developers. Consider the [http://owasp-esapi-java.googlecode.com/svn/trunk_doc/latest/org/owasp/esapi/Authenticator.html ESAPI Authenticator and User APIs]
 
  as good examples to emulate, use, or build upon.
 
  as good examples to emulate, use, or build upon.
 
# Strong efforts should also be made to avoid XSS flaws which can be used to steal session IDs. See A2.
 
# Strong efforts should also be made to avoid XSS flaws which can be used to steal session IDs. See A2.

Revision as of 18:27, 18 April 2010

««««
Top 10 Introduction
Top 10 Risks
»»»»


[[1]]

Threat Agents Attack Vectors Security Weakness Technical Impact Business Impacts
______ Exploitability
AVERAGE
Prevalence
COMMON
Detectability
AVERAGE
Impact
SEVERE
______
Consider anonymous external attackers, as well as users with their own accounts, who may attempt to steal accounts from others. Also consider insiders wanting to disguise their actions. Attacker uses leaks or flaws in the authentication or session management functions (e.g., exposed accounts, passwords, session IDs) to impersonate users. Developers frequently build custom authentication and session management schemes, but building these correctly is hard. As a result, these custom schemes frequently have flaws in areas such as logout, password management, timeouts, remember me, secret question, account update, etc. Finding such flaws can sometimes be difficult, as each implementation is unique. Such flaws may allow some or even all accounts to be attacked. Once successful, the attacker can do anything the victim could do. Privileged accounts are frequently targeted. Consider the business value of the affected data or application functions.

Also consider the business impact of public exposure of the vulnerability.

Am I Vulnerable to Broken Authentication and Session Management?

The primary assets to protect are credentials and session IDs.

  1. Are credentials always protected when stored using hashing or encryption? See A7.
  2. Can credentials be guessed or overwritten through weak account management functions (e.g., account creation, change password, recover password, weak session IDs)?
  3. Are session IDs exposed in the URL (e.g., URL rewriting)?
  4. Are session IDs vulnerable to session fixation attacks?
  5. Do session IDs timeout and can users log out?
  6. Are session IDs rotated after successful login?
  7. Are passwords, session IDs, and other credentials sent only over TLS connections? See A9.

See the [[2]] requirement areas V2 and V3 for more details.


How Do I Prevent Broken Authentication and Session Management?

{{{2}}}

Example Attack Scenarios

References


««««
Top 10 Introduction
Top 10 Risks
»»»»

© 2002-2010 OWASP Foundation This document is licensed under the Creative Commons Attribution-ShareAlike 3.0 license. Some rights reserved. CC-by-sa-3 0-88x31.png