CWE-706 is Use of Incorrectly-Resolved Name or Reference. The flaw arises when the product uses a name or reference to access a resource, but that name or reference resolves to a resource outside the intended control sphere. The database currently holds 72 vulnerabilities mapped to CWE-706 and none of them are in the CISA Known Exploited Vulnerabilities catalog.
No vulnerability data in CISA KEV for CWE-706
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.
The product relies on a name or reference to identify the resource it intends to access. If resolution maps that value to a resource outside the intended control sphere, the product may operate on the wrong object instead of the resource expected by its security or business logic. The issue is therefore a mismatch between the logically intended resource and the resource actually resolved, and it may originate in architecture, design, or implementation.
This weakness occurs when name or reference resolution directs an access operation to a resource outside the control sphere intended by the product. It is not specific to a programming language or technology and can be introduced during architecture and design or during implementation.
A misresolved name or reference can allow unauthorized reading of application data, affecting confidentiality. It can also allow unauthorized modification of application data, affecting integrity.
| Impact | Scope | Explanation |
|---|---|---|
| Read Application Data, Modify Application Data | Confidentiality, Integrity | - |
The official record does not specify mitigation guidance for this weakness.
Automated static analysis, commonly called Static Application Security Testing (SAST), can identify some instances by analyzing source or binary code without execution. It commonly models data flow and control flow, then searches for potentially vulnerable patterns connecting input sources to sinks where data interacts with external components or lower layers such as the operating system. This approach has limits and may not detect every incorrectly resolved name or reference.
| Method | Approach | Effectiveness |
|---|---|---|
| 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.) | - |
The official record does not provide representative observed vulnerability examples.
CWE™ Program, operated by The MITRE Corporation. Copyright © 2006–2026, The MITRE Corporation. The MITRE Corporation hereby grants you a non-exclusive, royalty-free license to use CWE for research, development, and commercial purposes. CWE Terms of Use.
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.
Review CyStack's security rating and practical recommendations for websites and edge assets.
Explore cybersecurity research from our team of security specialists.
Browse practical cybersecurity knowledge across CyStack's articles and guides.
en
