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

From OWASP
Jump to: navigation, search
(Examples)
 
(4 intermediate revisions by one user not shown)
Line 1: Line 1:
 +
{{Template:Vulnerability}}
 
{{Template:SecureSoftware}}
 
{{Template:SecureSoftware}}
{{Template:Vulnerability}}
 
 
[[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}}'''
 
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
  
 
[[ASDR_TOC_Vulnerabilities|Vulnerabilities Table of Contents]]
 
[[ASDR_TOC_Vulnerabilities|Vulnerabilities Table of Contents]]
 
[[ASDR Table of Contents]]
 
__TOC__
 
 
  
 
==Description==
 
==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.
  
Line 22: Line 15:
 
* Integrity: The resource in question, or other resources (through the corrupted one) may be changed in undesirable ways by a malicious user.
 
* 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.
 
* 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.
+
* 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==
 
==Risk Factors==
Line 33: Line 25:
  
 
==Examples==
 
==Examples==
 
+
TBD
===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]]==
 
==Related [[Attacks]]==

Latest revision as of 16:05, 28 February 2009

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



Last revision (mm/dd/yy): 02/28/2009

Vulnerabilities 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

TBD

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: