Symbolic Name not Mapping to Correct Object
Weakness ID: 386 (Weakness Base)Status: Draft
+ Description

Description Summary

A constant symbolic reference to an object is used, even though the reference can resolve to a different object over time.
+ Time of Introduction
  • Architecture and Design
  • Implementation
+ Applicable Platforms

Languages

All

+ Common Consequences
ScopeEffect
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.

+ Relationships
NatureTypeIDNameView(s) this relationship pertains toView(s)
ChildOfCategoryCategory361Time and State
Development Concepts (primary)699
ChildOfWeakness ClassWeakness Class706Use of Incorrectly-Resolved Name or Reference
Research Concepts (primary)1000
PeerOfWeakness BaseWeakness Base367Time-of-check Time-of-use (TOCTOU) Race Condition
Research Concepts1000
PeerOfWeakness VariantWeakness Variant486Comparison of Classes by Name
Research Concepts1000
PeerOfWeakness ClassWeakness Class610Externally Controlled Reference to a Resource in Another Sphere
Research Concepts1000
RequiredByCompound Element: CompositeCompound Element: Composite61UNIX Symbolic Link (Symlink) Following
Research Concepts1000
+ Taxonomy Mappings
Mapped Taxonomy NameNode IDFitMapped Node Name
CLASPSymbolic name not mapping to correct object
+ Content History
Submissions
Submission DateSubmitterOrganizationSource
CLASPExternally Mined
Modifications
Modification DateModifierOrganizationSource
2008-07-01Eric DalciCigitalExternal
updated Time of Introduction
2008-09-08CWE Content TeamMITREInternal
updated Common Consequences, Relationships, Taxonomy Mappings
Back to top