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

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.

Very High
Severity
3
occurrences in scenarios
Frequency
2
Affected Components
2
Affected Scenarios

Requirements and Mitigations

Requirements

Component properties that must be true for this threat to apply:

Mitigations

Component properties that mitigate this threat:

Affected Components

Component Description Boundary
doc_to_pixels.py Reads a suspicious documents and converts it to pixels gVisor sandbox
LibreOffice Converts documents to PDFs gVisor sandbox

Affected Scenarios

convert — affects: doc_to_pixels.py LibreOffice
convert_basic — affects: doc_to_pixels.py

Back to Summary