Difference between revisions of "Discrepancy Information Leaks"

From OWASP
Jump to: navigation, search
(Related Vulnerabilities)
Line 1: Line 1:
 
{{Template:Vulnerability}}
 
{{Template:Vulnerability}}
 +
 +
{{Template:Stub}}
 +
[[Category:FIXME|This is the text from the old template. This needs to be rewritten using the new template.]]
 +
 +
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
 +
 +
[[ASDR_TOC_Vulnerabilities|Vulnerabilities Table of Contents]]
 +
 +
[[ASDR Table of Contents]]
 +
__TOC__
  
  
Line 5: Line 15:
  
 
Application reveals details about its inner working by behaving differently, or sending different responses, to different user inputs.  
 
Application reveals details about its inner working by behaving differently, or sending different responses, to different user inputs.  
 
==Related Threats==
 
  
 
Attackers try to observe the internal working of the application to obtain clues of attacks.  
 
Attackers try to observe the internal working of the application to obtain clues of attacks.  
  
==Related Attacks==
 
  
Attacks that can take advantage of the information revealed in this vulnerability. For example, if an attacker knows whether a user name exists or not through the login response, he can accordingly change his strategy of a brute-force attack.
+
==Risk Factors==
  
==Related Vulnerabilities==
+
TBD
* [[Error Message Infoleaks]]
+
  
==Related Countermeasures==
+
 
 +
==Examples==
 +
 
 +
===Short example name===
 +
: A short example description, small picture, or sample code with [http://www.site.com links]
 +
 
 +
===Short example name===
 +
: A short example description, small picture, or sample code with [http://www.site.com links]
 +
 
 +
 
 +
==Related [[Attacks]]==
 +
 
 +
* [[Attack 1]]
 +
* [[Attack 2]]
 +
* Attacks that can take advantage of the information revealed in this vulnerability. For example, if an attacker knows whether a user name exists or not through the login response, he can accordingly change his strategy of a brute-force attack.
 +
 
 +
 
 +
 
 +
==Related [[Vulnerabilities]]==
 +
*  [[Error Message Infoleaks]]
 +
 
 +
==Related [[Controls]]==
 
* [[Error Handling]]
 
* [[Error Handling]]
  
==Categories==
+
==Related [[Technical Impacts]]==
 +
* [[Technical Impact 1]]
 +
* [[Technical Impact 2]]
  
{{Template:Stub}}
+
 
 +
==References==
 +
TBD
 +
 
 +
[[Category:FIXME|add links
 +
 
 +
In addition, one should classify vulnerability based on the following subcategories: Ex:<nowiki>[[Category:Error Handling Vulnerability]]</nowiki>
 +
 
 +
Availability Vulnerability
 +
 
 +
Authorization Vulnerability
 +
 
 +
Authentication Vulnerability
 +
 
 +
Concurrency Vulnerability
 +
 
 +
Configuration Vulnerability
 +
 
 +
Cryptographic Vulnerability
 +
 
 +
Encoding Vulnerability
 +
 
 +
Error Handling Vulnerability
 +
 
 +
Input Validation Vulnerability
 +
 
 +
Logging and Auditing Vulnerability
 +
 
 +
Session Management Vulnerability]]
 +
 
 +
__NOTOC__
 +
 
 +
 
 +
[[Category:OWASP ASDR Project]]

Revision as of 17:54, 23 September 2008

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


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

Last revision (mm/dd/yy): 09/23/2008

Vulnerabilities Table of Contents

ASDR Table of Contents

Contents


Description

Application reveals details about its inner working by behaving differently, or sending different responses, to different user inputs.

Attackers try to observe the internal working of the application to obtain clues of attacks.


Risk Factors

TBD


Examples

Short example name

A short example description, small picture, or sample code with links

Short example name

A short example description, small picture, or sample code with links


Related Attacks

  • Attack 1
  • Attack 2
  • Attacks that can take advantage of the information revealed in this vulnerability. For example, if an attacker knows whether a user name exists or not through the login response, he can accordingly change his strategy of a brute-force attack.


Related Vulnerabilities

Related Controls

Related Technical Impacts


References

TBD