CWE-386: Symbolic Name not Mapping to Correct Object

A constant symbolic reference to an object is used, even though the reference can resolve to a different object over time.

Symbolic Name not Mapping to Correct Object is typically found by tracing untrusted input from where it enters the system to the point where it is used without the check or neutralization this weakness describes, combining manual code review with dynamic testing.

Gain Privileges or Assume Identity: The attacker can gain access to otherwise unauthorized resources. Modify Application Data, Modify Files or Directories, Read Application Data, Read Files or Directories, Other: 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. Modify Application Data, Other: The resource in question, or other resources (through the corrupted one) may be changed in undesirable ways by a malicious user. Hide Activities: If a file or other resource is written in this method, as opposed to a valid way, logging of the activity may not occur. Modify Files or Directories: In some cases it may be possible to delete files that a malicious user might not otherwise have access to -- such as log files.

This weakness is not covered by the automated black-box pentest. IntegSec pentesters cover it in a manual engagement.