Home > CAPEC List > CAPEC-177: Create files with the same name as files protected with a higher classification (Version 2.9)  

CAPEC-177: Create files with the same name as files protected with a higher classification

 
Create files with the same name as files protected with a higher classification
Definition in a New Window Definition in a New Window
Attack Pattern ID: 177
Abstraction: Standard
Status: Draft
Completeness: Stub
Presentation Filter:
+ Summary

An attacker exploits file location algorithms in an operating system or application by creating a file with the same name as a protected or privileged file. The attacker could manipulate the system if the attacker-created file is trusted by the operating system or an application component that attempts to load the original file. Applications often load or include external files, such as libraries or configuration files. These files should be protected against malicious manipulation. However, if the application only uses the name of the file when locating it, an attacker may be able to create a file with the same name and place it in a directory that the application will search before the directory with the legitimate file is searched. Because the attackers' file is discovered first, it would be used by the target application. This attack can be extremely destructive if the referenced file is executable and/or is granted special privileges based solely on having a particular name.

+ Attack Prerequisites
  • The target application must exclude external files. Most non-trivial applications meet this criterion.

  • The target application does not verify that a located file is the one it was looking for through means other than the name. Many applications fail to perform checks of this type.

  • The directories the target application searches to find the included file include directories writable by the attacker which are searched before the protected directory containing the actual files. It is much less common for applications to meet this criterion, but if an attacker can manipulate the application's search path (possibly by controlling environmental variables) then they can force this criterion to be met.

+ Typical Severity

Very High

+ Resources Required

The attacker must have sufficient access to place an arbitrarily named file somewhere early in the application's search path.

+ References
[R.177.2] ATT&CK Project. "Masquerading (1036)". MITRE. <https://attack.mitre.org/wiki/Masquerading>.
+ Content History
Submissions
SubmitterOrganizationDateSource
CAPEC Content TeamThe MITRE Corporation2014-06-23Internal_CAPEC_Team
Modifications
ModifierOrganizationDateCommentsSource
CAPEC Content TeamThe MITRE Corporation2015-11-09Updated ReferencesInternal

More information is available — Please select a different filter.
Page Last Updated or Reviewed: December 07, 2015