Difference between revisions of "Authentication Bypass via Assumed-Immutable Data"

From OWASP
Jump to: navigation, search
Line 1: Line 1:
{{Template:Vulnerability}}
 
 
{{Template:Stub}}
 
{{Template:Stub}}
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
+
{{Template:Vulnerability}}
[[Category:FIXME|This is the text from the old template. This needs to be rewritten using the new template.]]
+
 
 
__TOC__
 
__TOC__
  
 +
[[ASDR Table of Contents]]
  
 +
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
 +
 +
[[Category:FIXME|This is the text from the old template. This needs to be rewritten using the new template.]]
 
[[Category:FIXME|Stub article, needs review]]
 
[[Category:FIXME|Stub article, needs review]]
  
[[ASDR_TOC_Vulnerabilities|Vulnerabilities Table of Contents]]
 
 
[[ASDR Table of Contents]]
 
  
 
==Description==
 
==Description==

Revision as of 06:32, 29 October 2008

This article is a stub. You can help OWASP by expanding it or discussing it on its Talk page.


This is a Vulnerability. To view all vulnerabilities, please see the Vulnerability Category page.


ASDR Table of Contents

Last revision (mm/dd/yy): 10/29/2008


Description

Assumed-immutable authentication data can be modified by attackers to bypass the authentication. Most of the time, this vulnerability results from inappropriate session management, i.e., important data that is used for authentication decisions is sent to the client side and subject to user modification. This kind of data should be stored in the server-side session as much as possible.


Risk Factors

TBD


Examples

TBD


Related Attacks


Related Vulnerabilities


Related Controls


Related Technical Impacts


References

TBD