| Name |
Remote Code Inclusion |
|
| Likelyhood of attack |
Typical severity |
| High |
Medium |
|
| Summary |
The attacker forces an application to load arbitrary code files from a remote location. The attacker could use this to try to load old versions of library files that have known vulnerabilities, to load malicious files that the attacker placed on the remote machine, or to otherwise change the functionality of the targeted application in unexpected ways. |
| Prerequisites |
Target application server must allow remote files to be included.The malicious file must be placed on the remote machine previously. |
| Solutions | Minimize attacks by input validation and sanitization of any user data that will be used by the target application to locate a remote file to be included. |
| Related Weaknesses |
|
CWE ID
|
Description
|
| CWE-829 |
Inclusion of Functionality from Untrusted Control Sphere |
|
| Related CAPECS |
|
CAPEC ID
|
Description
|
| CAPEC-175 |
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. |
|
| Taxonomy: WASC |
|
Entry ID
|
Entry Name
|
| 05 |
Remote File Inclusion |
|