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 "Top 10 2010-A3-Broken Authentication and Session Management"
From OWASP
| 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=}} | ||
| − | |||
| − | |||
<center> | <center> | ||
| Line 29: | Line 27: | ||
</center> | </center> | ||
| − | {{Top_10_2010:SubsectionVulnerableTemplate| | + | {{Top_10_2010:SubsectionVulnerableTemplate|aaa| |
The primary assets to protect are credentials and session IDs. | The primary assets to protect are credentials and session IDs. | ||
#Are credentials always protected when stored using hashing or encryption? See A7. | #Are credentials always protected when stored using hashing or encryption? See A7. | ||
| Line 42: | Line 40: | ||
}} | }} | ||
| − | {{Top_10_2010:SubsectionPreventionTemplate| | + | {{Top_10_2010:SubsectionPreventionTemplate|bbb| |
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: | ||
Revision as of 00:36, 19 April 2010
NOTE: THIS IS NOT THE LATEST VERSION. Please visit the OWASP Top 10 project page to find the latest edition.
| 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 aaa?
The primary assets to protect are credentials and session IDs.
- Are credentials always protected when stored using hashing or encryption? See A7.
- Can credentials be guessed or overwritten through weak account management functions (e.g., account creation, change password, recover password, weak session IDs)?
- Are session IDs exposed in the URL (e.g., URL rewriting)?
- Are session IDs vulnerable to session fixation attacks?
- Do session IDs timeout and can users log out?
- Are session IDs rotated after successful login?
- Are passwords, session IDs, and other credentials sent only over TLS connections? See A9.
See the [[1]] requirement areas V2 and V3 for more details.
How Do I Prevent bbb?
{{{2}}}
Example Attack Scenarios
References
