CWE-367 检查时间与使用时间(TOCTOU)的竞争条件

admin 2021年12月16日16:01:14CWE(弱点枚举)评论191 views6573字阅读21分54秒阅读模式

CWE-367 检查时间与使用时间(TOCTOU)的竞争条件

Time-of-check Time-of-use (TOCTOU) Race Condition

结构: Simple

Abstraction: Base

状态: Incomplete

被利用可能性: Medium


The software 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. This can cause the software to perform invalid actions when the resource is in an unexpected state.


This weakness can be security-relevant when an attacker can influence the state of the resource between check and use. This can happen with shared resources such as files, memory, or even variables in multithreaded programs.


  • cwe_Nature: ChildOf cwe_CWE_ID: 362 cwe_View_ID: 1000 cwe_Ordinal: Primary

  • cwe_Nature: ChildOf cwe_CWE_ID: 362 cwe_View_ID: 1003 cwe_Ordinal: Primary

  • cwe_Nature: ChildOf cwe_CWE_ID: 362 cwe_View_ID: 699 cwe_Ordinal: Primary


Language: {'cwe_Class': 'Language-Independent', 'cwe_Prevalence': 'Undetermined'}


范围 影响 注释
['Integrity', 'Other'] ['Alter Execution Logic', 'Unexpected State'] The attacker can gain access to otherwise unauthorized resources.
['Integrity', 'Other'] ['Modify Application Data', 'Modify Files or Directories', 'Modify Memory', 'Other'] Race conditions such as this kind may be employed to gain read or write access to resources which are not normally readable or writable by the user in question.
['Integrity', 'Other'] Other The resource in question, or other resources (through the corrupted one), may be changed in undesirable ways by a malicious user.
Non-Repudiation Hide Activities If a file or other resource is written in this method, as opposed to in a valid way, logging of the activity may not occur.
['Non-Repudiation', 'Other'] Other In some cases it may be possible to delete files a malicious user might not otherwise have access to, such as log files.




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.

Architecture and Design


Limit the interleaving of operations on files from multiple processes.

['Implementation', 'Architecture and Design']


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.

Architecture and Design


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.


The following code checks a file, then updates its contents.

bad C

struct stat *sb;
lstat("...",sb); // it has not been updated since the last time it was read
printf("stated filen");
if (sb->st_mtimespec==...){

print("Now updating thingsn");


Potentially the file could have been updated between the time of the check and the lstat, especially since the printf has latency.

The following code is from a program installed setuid root. The program performs certain file operations on behalf of non-privileged users, and uses access checks to ensure that it does not use its root privileges to perform operations that should otherwise be unavailable the current user. The program uses the access() system call to check if the person running the program has permission to access the specified file before it opens the file and performs the necessary operations.

bad C

if(!access(file,W_OK)) {

f = fopen(file,"w+");

else {

fprintf(stderr,"Unable to open file %s.n",file);


The call to access() behaves as expected, and returns 0 if the user running the program has the necessary permissions to write to the file, and -1 otherwise. However, because both access() and fopen() operate on filenames rather than on file handles, there is no guarantee that the file variable still refers to the same file on disk when it is passed to fopen() that it did when it was passed to access(). If an attacker replaces file after the call to access() with a symbolic link to a different file, the program will use its root privileges to operate on the file even if it is a file that the attacker would otherwise be unable to modify. By tricking the program into performing an operation that would otherwise be impermissible, the attacker has gained elevated privileges. This type of vulnerability is not limited to programs with root privileges. If the application is capable of performing any operation that the attacker would not otherwise be allowed perform, then it is a possible target.

This code prints the contents of a file if a user has permission.

bad PHP

function readFile($filename){

$user = getCurrentUser();

//resolve file if its a symbolic link


$filename = readlink($filename);


if(fileowner($filename) == $user){

echo file_get_contents($realFile);


echo 'Access denied';
return false;



This code attempts to resolve symbolic links before checking the file and printing its contents. However, an attacker may be able to change the file from a real file to a symbolic link between the calls to is_link() and file_get_contents(), allowing the reading of arbitrary files. Note that this code fails to log the attempted access (CWE-778).


标识 说明 链接
CVE-2003-0813 A multi-threaded race condition allows remote attackers to cause a denial of service (crash or reboot) by causing two threads to process the same RPC request, which causes one thread to use memory after it has been freed.
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.


TOCTOU issues do not always involve symlinks, and not every symlink issue is a TOCTOU problem.
Research Gap
Non-symlink TOCTOU issues are not reported frequently, but they are likely to occur in code that attempts to be secure.


映射的分类名 ImNode ID Fit Mapped Node Name
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
CERT C Secure Coding FIO01-C Be careful using functions that use file names for identification
Software Fault Patterns SFP20 Race Condition Window


  • CAPEC-27
  • CAPEC-29



特别标注: 本站(CN-SEC.COM)所有文章仅供技术研究,若将其信息做其他用途,由用户承担全部法律及连带责任,本站不承担任何法律及连带责任,请遵守中华人民共和国安全法.
  • 我的微信
  • 微信扫一扫
  • weinxin
  • 我的微信公众号
  • 微信扫一扫
  • weinxin
  • 本文由 发表于 2021年12月16日16:01:14
  • 转载请保留本文链接(CN-SEC中文网:感谢原作者辛苦付出):
                  CWE-367 检查时间与使用时间(TOCTOU)的竞争条件


匿名网友 填写信息

:?: :razz: :sad: :evil: :!: :smile: :oops: :grin: :eek: :shock: :???: :cool: :lol: :mad: :twisted: :roll: :wink: :idea: :arrow: :neutral: :cry: :mrgreen: