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.
How it's found
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.
Consequences
- 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.
Where this fits in a TurboPentest engagement
TurboPentest's agentic pentest is powerful and covers a broad range of issues automatically. This particular class is best confirmed in a manual IntegSec engagement, where human pentesters apply deeper methodology and a larger context window than any automated pass.
Frequently asked questions
What is CWE-386?
A constant symbolic reference to an object is used, even though the reference can resolve to a different object over time.
How do you find Symbolic Name not Mapping to Correct Object?
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.
What is the impact of CWE-386?
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.
Does TurboPentest test for Symbolic Name not Mapping to Correct Object?
TurboPentest's agentic pentest is powerful and covers a broad range of issues automatically. This particular class is best confirmed in a manual IntegSec engagement, where human pentesters apply deeper methodology and a larger context window than any automated pass.
Related CWEs
About this reference
These security references are maintained by IntegSec, an offensive-security firm whose team holds CISSP, OSCP, and OSCE certifications and has run thousands of penetration tests. Content is kept current as tools, standards, and attack techniques evolve.
Find these issues before an attacker does
TurboPentest runs an agentic AI pentest against your target and reports findings with proof, from $99 per target.
Start a pentest