| Name |
Leveraging Race Conditions via Symbolic Links |
|
| Likelyhood of attack |
Typical severity |
| Medium |
High |
|
| Summary |
This attack leverages the use of symbolic links (Symlinks) in order to write to sensitive files. An attacker can create a Symlink link to a target file not otherwise accessible to them. When the privileged program tries to create a temporary file with the same name as the Symlink link, it will actually write to the target file pointed to by the attackers' Symlink link. If the attacker can insert malicious content in the temporary file they will be writing to the sensitive file by using the Symlink. The race occurs because the system checks if the temporary file exists, then creates the file. The attacker would typically create the Symlink during the interval between the check and the creation of the temporary file. |
| Prerequisites |
The attacker is able to create Symlink links on the target host. Tainted data from the attacker is used and copied to temporary files. The target host does insecure temporary file creation. |
| Execution Flow |
| Step |
Phase |
Description |
Techniques |
| 1 |
Explore |
[Verify that target host's platform supports symbolic links.] This attack pattern is only applicable on platforms that support symbolic links. |
- Research target platform to determine whether it supports symbolic links.
- Create a symbolic link and ensure that it works as expected on the given platform.
|
| 2 |
Explore |
[Examine application's file I/O behavior] Analyze the application's file I/O behavior to determine where it stores files, as well as the operations it performs to read/write files. |
- Use kernel tracing utility such as ktrace to monitor application behavior.
- Use debugging utility such as File Monitor to monitor the application's filesystem I/O calls
- Watch temporary directories to see when temporary files are created, modified and deleted.
- Analyze source code for open-source systems like Linux, Apache, etc.
|
| 3 |
Experiment |
[Verify ability to write to filesystem] The attacker verifies ability to write to the target host's file system. |
- Create a file that does not exist in the target directory (e.g. "touch temp.txt" in UNIX-like systems)
- On platforms that differentiate between file creation and file modification, if the target file that the application writes to already exists, attempt to modify it.
- Verify permissions on target directory
|
| 4 |
Exploit |
[Replace file with a symlink to a sensitive system file.] Between the time that the application checks to see if a file exists (or if the user has access to it) and the time the application actually opens the file, the attacker replaces the file with a symlink to a sensitive system file. |
- Create an infinite loop containing commands such as "rm -f tempfile.dat; ln -s /etc/shadow tempfile.dat". Wait for an instance where the following steps occur in the given order: (1) Application ensures that tempfile.dat exists and that the user has access to it, (2) "rm -f tempfile.dat; ln -s /etc/shadow tempfile.dat", and (3) Application opens tempfile.dat for writing, and inadvertently opens /etc/shadow for writing instead.
- Use other techniques with debugging tools to replace the file between the time the application checks the file and the time the application opens it.
|
|
| Solutions | Use safe libraries when creating temporary files. For instance the standard library function mkstemp can be used to safely create temporary files. For shell scripts, the system utility mktemp does the same thing. Access to the directories should be restricted as to prevent attackers from manipulating the files. Denying access to a file can prevent an attacker from replacing that file with a link to a sensitive file. Follow the principle of least privilege when assigning access rights to files. Ensure good compartmentalization in the system to provide protected areas that can be trusted. |
| Related Weaknesses |
|
CWE ID
|
Description
|
| CWE-61 |
UNIX Symbolic Link (Symlink) Following |
| CWE-367 |
Time-of-check Time-of-use (TOCTOU) Race Condition |
| CWE-662 |
Improper Synchronization |
| CWE-667 |
Improper Locking |
| CWE-689 |
Permission Race Condition During Resource Copy |
|
| Related CAPECS |
|
CAPEC ID
|
Description
|
| CAPEC-29 |
This attack targets a race condition occurring between the time of check (state) for a resource and the time of use of a resource. A typical example is file access. The adversary can leverage a file access race condition by "running the race", meaning that they would modify the resource between the first time the target program accesses the file and the time the target program uses the file. During that period of time, the adversary could replace or modify the file, causing the application to behave unexpectedly. |
|