Difference between revisions of "Symbolic name not mapping to correct object"

From OWASP
Jump to: navigation, search
Line 1: Line 1:
 
{{Template:SecureSoftware}}
 
{{Template:SecureSoftware}}
 +
{{Template:Vulnerability}}
  
==Overview==  
+
[[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__
 +
 
 +
 
 +
==Description==
  
 
A constant symbolic reference to an object is used, even though the underlying object changes over time.
 
A constant symbolic reference to an object is used, even though the underlying object changes over time.
  
==Consequences ==
+
'''Consequences'''
  
* Access control: The attacker can gain access to otherwise unauthorized resources.
+
* Access control: The attacker can gain access to otherwise unauthorized resources.
 +
* Authorization: Race conditions such as this kind may be employed to gain read or write access to resources not normally readable or writable by the user in question.
 +
* Integrity: The resource in question, or other resources (through the corrupted one) may be changed in undesirable ways by a malicious user.
 +
* Accountability: If a file or other resource is written in this method, as opposed to a valid way, logging of the activity may not occur.
 +
* Non-repudiation: In some cases it may be possible to delete files that a malicious user might not otherwise have access to - such as log files.
  
* Authorization: Race conditions such as this kind may be employed to gain read or write access to resources not normally readable or writable by the user in question.
 
  
* Integrity: The resource in question, or other resources (through the corrupted one) may be changed in undesirable ways by a malicious user.
+
==Risk Factors==
  
* Accountability: If a file or other resource is written in this method, as opposed to a valid way, logging of the activity may not occur.
+
* Talk about the [[OWASP Risk Rating Methodology|factors]] that make this vulnerability likely or unlikely to actually happen
 +
* Discuss the technical impact of a successful exploit of this vulnerability
 +
* Consider the likely [business impacts] of a successful attack
  
* Non-repudiation: In some cases it may be possible to delete files that a malicious user might not otherwise have access to - such as log files.
 
  
==Exposure period ==
+
==Examples==
  
==Platform ==
+
===Short example name===
 +
: A short example description, small picture, or sample code with [http://www.site.com links]
  
==Required resources ==
+
===Short example name===
 +
: A short example description, small picture, or sample code with [http://www.site.com links]
  
==Severity ==
 
  
==Likelihood  of exploit ==
+
==Related [[Attacks]]==
  
==Avoidance and mitigation ==
+
* [[Attack 1]]
 +
* [[Attack 2]]
  
==Discussion ==
 
  
See more specific instances.
+
==Related [[Vulnerabilities]]==
  
==Examples ==
+
* Time of check, time of use race condition
 +
* Comparing classes by name
  
Not available.
 
  
==Related problems ==
+
==Related [[Controls]]==
  
* Time of check, time of use race condition
+
* [[Control 1]]
 +
* [[Control 2]]
  
* Comparing classes by name
 
  
 +
==Related [[Technical Impacts]]==
  
[[Category:Vulnerability]]
+
* [[Technical Impact 1]]
 +
* [[Technical Impact 2]]
  
[[Category:General Logic Error Vulnerability]]
 
  
 +
==References==
 +
Note: A reference to related [http://cwe.mitre.org/ CWE] or [http://capec.mitre.org/ CAPEC] article should be added when exists. Eg:
 +
 +
* [http://cwe.mitre.org/data/definitions/79.html CWE 79].
 +
* http://www.link1.com
 +
* [http://www.link2.com Title for the link2]
 +
 +
[[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]]
 +
[[Category:Vulnerability]]
 +
[[Category:General Logic Error Vulnerability]]
 
[[Category:OWASP_CLASP_Project]]
 
[[Category:OWASP_CLASP_Project]]

Revision as of 19:58, 30 September 2008

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

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

Vulnerabilities Table of Contents

ASDR Table of Contents


Description

A constant symbolic reference to an object is used, even though the underlying object changes over time.

Consequences

  • Access control: The attacker can gain access to otherwise unauthorized resources.
  • Authorization: Race conditions such as this kind may be employed to gain read or write access to resources not normally readable or writable by the user in question.
  • Integrity: The resource in question, or other resources (through the corrupted one) may be changed in undesirable ways by a malicious user.
  • Accountability: If a file or other resource is written in this method, as opposed to a valid way, logging of the activity may not occur.
  • Non-repudiation: In some cases it may be possible to delete files that a malicious user might not otherwise have access to - such as log files.


Risk Factors

  • Talk about the factors that make this vulnerability likely or unlikely to actually happen
  • Discuss the technical impact of a successful exploit of this vulnerability
  • Consider the likely [business impacts] of a successful attack


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


Related Vulnerabilities

  • Time of check, time of use race condition
  • Comparing classes by name


Related Controls


Related Technical Impacts


References

Note: A reference to related CWE or CAPEC article should be added when exists. Eg: