CWE-706: Use of Incorrectly-Resolved Name or Reference
| Abstraction | Structure | Status |
|---|---|---|
| None | Simple | Incomplete |
Description
The product uses a name or reference to access a resource, but the name/reference resolves to a resource that is outside of the intended control sphere.
Related Weaknesses
| Nature | ID | View ID | Name |
|---|---|---|---|
| ChildOf | CWE-664 | 1000 | Improper Control of a Resource Through its Lifetime |
| PeerOf | CWE-99 | 1000 | Improper Control of Resource Identifiers (‘Resource Injection’) |
Modes of Introduction
| Phase | Note |
|---|---|
| Architecture and Design | - |
| Implementation | - |
Applicable Platforms
Languages
Class: Not Language-Specific
Technologies
Class: Not Technology-Specific
Common Consequences
| Scope | Impact | Note |
|---|---|---|
| Confidentiality, Integrity | Read Application Data, Modify Application Data |
Detection Methods
Automated Static Analysis
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect “sources” (origins of input) with “sinks” (destinations where the data interacts with external components, a lower layer such as the OS, etc.)