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

Jump to: navigation, search
Line 46: Line 46:
[[Category:Synchronization and Timing Errror]]
[[Category:General Logic Error Vulnerability]]

Revision as of 14:41, 16 June 2006


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


  • 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.

Exposure period


Required resources


Likelihood of exploit

Avoidance and mitigation


See more specific instances.


Not available.

Related problems

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