CWEweakness

CWE-386 Symbolic Name not Mapping to Correct Object

Official page ↗
Abstraction
Base
Structure
Simple
Status
Draft
Languages
Not Language-Specific
CWE version
5.0

Description

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

Common consequences

• Access Control: Gain Privileges or Assume Identity — The attacker can gain access to otherwise unauthorized resources. • Integrity, Confidentiality, Other: 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. • Integrity, Other: 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. • Non-Repudiation: 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. • Non-Repudiation, Integrity: 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.

Related

Child of · CWE (1)

  • CWE-706 Use of Incorrectly-Resolved Name or Reference weakness

Peer of · CWE (3)

  • CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition weakness
  • CWE-486 Comparison of Classes by Name weakness
  • CWE-610 Externally Controlled Reference to a Resource in Another Sphere weakness

Referenced by CVE · weakness (4)

  • CVE-2026-116486 Objenesis before 3.6 contains a type confusion vulnerability that allows code in one class loader to substitute objects into another by… vulnerability
  • CVE-2026-94114 Symbolic name not mapping to correct class. vulnerability
  • CVE-2026-53081 In the Linux kernel, the following vulnerability has been resolved: bpf: Enforce regsafe base id consistency for BPF_ADD_CONST scalars When… vulnerability
  • CVE-2024-3852 GetBoundName could return the wrong version of an object when JIT optimizations were applied. vulnerability

Referenced by CWE · requires (1)

  • CWE-61 UNIX Symbolic Link (Symlink) Following weakness