Description
The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.
Potential Impact
Integrity, Other
Alter Execution Logic, Unexpected State
Integrity, Other
Modify Application Data, Modify Files or Directories, Modify Memory, Other
Integrity, Other
Other
Non-Repudiation
Hide Activities
Non-Repudiation, Other
Other
Other
Unexpected State
Demonstrative Examples
struct stat *sb;...lstat("...",sb); // it has not been updated since the last time it was readprintf("stated file\n");if (sb->st_mtimespec==...){print("Now updating things\n");updateThings();}if(!access(file,W_OK)) {f = fopen(file,"w+");operate(f);...}else {
fprintf(stderr,"Unable to open file %s.\n",file);
}function readFile($filename){
$user = getCurrentUser();
//resolve file if its a symbolic link
if(is_link($filename)){$filename = readlink($filename);}
if(fileowner($filename) == $user){echo file_get_contents($realFile);return;}else{echo 'Access denied';return false;}
}#include <sys/types.h>
#include <sys/stat.h>
...
struct stat sb;
stat("MYFILE.txt",&sb);
printf("file change time: %d\n",sb->st_ctime);
switch(sb->st_ctime % 2){
case 0: printf("Option 1\n"); break;
case 1: printf("Option 2\n"); break;
default: printf("this should be unreachable?\n"); break;
}Mitigations & Prevention
The most basic advice for TOCTOU vulnerabilities is to not perform a check before the use. This does not resolve the underlying issue of the execution of a function on a resource whose state and identity cannot be assured, but it does help to limit the false sense of security given by the check.
When the file being altered is owned by the current user and group, set the effective gid and uid to that of the current user and group when executing this statement.
Limit the interleaving of operations on files from multiple processes.
If you cannot perform operations atomically and you must share access to the resource between multiple processes or threads, then try to limit the amount of time (CPU cycles) between the check and use of the resource. This will not fix the problem, but it could make it more difficult for an attack to succeed.
Recheck the resource after the use call to verify that the action was taken appropriately.
Ensure that some environmental locking mechanism can be used to protect resources effectively.
Ensure that locking occurs before the check, as opposed to afterwards, such that the resource, as checked, is the same as it is when in use.
Detection Methods
- Automated Static Analysis High — Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then sea
Real-World CVE Examples
| CVE ID | Description |
|---|---|
| CVE-2015-1743 | TOCTOU in sandbox process allows installation of untrusted browser add-ons by replacing a file after it has been verified, but before it is executed |
| CVE-2003-0813 | Chain: A multi-threaded race condition (CWE-367) allows attackers to cause two threads to process the same RPC request, which causes a use-after-free (CWE-416) in one thread |
| CVE-2004-0594 | PHP flaw allows remote attackers to execute arbitrary code by aborting execution before the initialization of key data structures is complete. |
| CVE-2008-2958 | chain: time-of-check time-of-use (TOCTOU) race condition in program allows bypass of protection mechanism that was designed to prevent symlink attacks. |
| CVE-2008-1570 | chain: time-of-check time-of-use (TOCTOU) race condition in program allows bypass of protection mechanism that was designed to prevent symlink attacks. |
Related Weaknesses
Taxonomy Mappings
- PLOVER: — Time-of-check Time-of-use race condition
- 7 Pernicious Kingdoms: — File Access Race Conditions: TOCTOU
- CLASP: — Time of check, time of use race condition
- CLASP: — Race condition in switch
- CERT C Secure Coding: FIO01-C — Be careful using functions that use file names for identification
- Software Fault Patterns: SFP20 — Race Condition Window
Frequently Asked Questions
What is CWE-367?
CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition) is a software weakness identified by MITRE's Common Weakness Enumeration. It is classified as a Base-level weakness. The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.
How can CWE-367 be exploited?
Attackers can exploit CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition) to alter execution logic, unexpected state. This weakness is typically introduced during the Implementation phase of software development.
How do I prevent CWE-367?
Key mitigations include: The most basic advice for TOCTOU vulnerabilities is to not perform a check before the use. This does not resolve the underlying issue of the execution of a function on a resource whose state and ident
What is the severity of CWE-367?
CWE-367 is classified as a Base-level weakness (Medium abstraction). It has been observed in 5 real-world CVEs.