CAPEC-175 Metadata
Likelihood of Attack
Medium
Typical Severity
Very High
Overview
Summary
An adversary exploits a weakness on the target to force arbitrary code to be retrieved locally or from a remote location and executed. This differs from code injection in that code injection involves the direct inclusion of code while code inclusion involves the addition or replacement of a reference to a code file, which is subsequently loaded by the target and used as part of the code of some application.
Prerequisites
The target application must include external code/libraries that are executed when the application runs and the adversary must be able to influence the specific files that get included. The victim must run the targeted application, possibly using the crafted parameters that the adversary uses to identify the code to include.
Potential Solutions / Mitigations
No specific solutions listed.
Related Weaknesses (CWE)
| CWE ID | Description |
|---|---|
| CWE-829 | Inclusion of Functionality from Untrusted Control Sphere |
Stay Ahead of Attack Patterns
Understanding CAPEC patterns helps security professionals anticipate and thwart potential attacks. Leverage these insights to enhance threat modeling, strengthen your software development lifecycle, and train your security teams effectively.