Weakness · High
CWE-386: Symbolic Name not Mapping to Correct Object
What it is
A constant symbolic reference to an object is used, even though the reference can resolve to a different object over time.
- Severity (our rating)
- High
- Likelihood of exploit
- Not rated by MITRE
- Introduced during
- Architecture and Design, Implementation
- Exploited in the wild
- No CVE in CISA's catalog
What an attacker can do
- Gain Privileges or Assume Identity (Access Control)
- Modify Application Data (Integrity, Confidentiality, Other)
- Modify Files or Directories (Integrity, Confidentiality, Other, Non-Repudiation)
- Read Application Data (Integrity, Confidentiality, Other)
- Read Files or Directories (Integrity, Confidentiality, Other)
- Other (Integrity, Confidentiality, Other)
- Hide Activities (Non-Repudiation)
How to prevent it
MITRE lists no specific mitigation for this weakness. Treat it like its parent weaknesses below: validate input, keep the design simple and review the code where it could appear.
H2 Security
Found it in your code?
We review where it appears, fix it with your team, and check it was not already used against you.
Talk to our teamT Academy
Stop writing it in the first place
Learn to build software and systems without weaknesses like this one, with practice on real hosts in your browser, every objective checked on the machine.
Start freeSource: MITRE Common Weakness Enumeration, CWE version 4.19.1. CWE is a trademark of The MITRE Corporation.