Home > CAPEC List > CAPEC-251: Local Code Inclusion (Version 2.10)  

CAPEC-251: Local Code Inclusion

Local Code Inclusion
Definition in a New Window Definition in a New Window
Attack Pattern ID: 251
Abstraction: Standard
Status: Draft
Completeness: Stub
Presentation Filter:
+ Summary

The attacker forces an application to load arbitrary code files from the local machine. The attacker could use this to try to load old versions of library files that have known vulnerabilities, to load files that the attacker placed on the local machine during a prior attack, or to otherwise change the functionality of the targeted application in unexpected ways.

+ Attack Prerequisites
  • The targeted application must have a bug that allows an attacker to control which code file is loaded at some juncture.

  • Some variants of this attack may require that old versions of some code files be present and in predictable locations.

+ Typical Severity


+ Resources Required

The attacker needs to have enough access to the target application to control the identity of a locally included file. The attacker may also need to be able to upload arbitrary code files to the target machine, although any location for these files may be acceptable.

+ References
[R.251.1] ATT&CK Project. "DLL Injection (1055)". MITRE. <https://attack.mitre.org/wiki/DLL_injection>.
+ Content History
CAPEC Content TeamThe MITRE Corporation2014-06-23Internal_CAPEC_Team
CAPEC Content TeamThe MITRE Corporation2015-11-09Updated ReferencesInternal
More information is available — Please select a different filter.
Page Last Updated or Reviewed: May 01, 2017