Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

325 vulnerabilities classified as CWE-367 (检查时间与使用时间(TOCTOU)的竞争条件). AI Chinese analysis included.

CWE-367 represents a logic flaw where a system verifies a resource’s state before accessing it, allowing the state to change maliciously between the verification and actual usage. Attackers typically exploit this race condition by manipulating the resource, such as swapping a file or altering permissions, during the narrow window between the check and the use. This enables unauthorized access or privilege escalation, as the application proceeds based on outdated, validated assumptions. To mitigate this vulnerability, developers must ensure atomic operations, ensuring that the check and use occur simultaneously without interruption. Implementing robust locking mechanisms, utilizing secure system calls that combine verification and access, or adopting file descriptor-based approaches can effectively prevent state changes, thereby eliminating the race condition and securing the resource against temporal manipulation.

MITRE CWE 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.
Common Consequences (6)
Integrity, OtherAlter Execution Logic, Unexpected State
The attacker can gain access to otherwise unauthorized resources.
Integrity, OtherModify 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, OtherOther
The resource in question, or other resources (through the corrupted one), may be changed in undesirable ways by a malicious user.
Non-RepudiationHide 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, OtherOther
In some cases it may be possible to delete files a malicious user might not otherwise have access to, such as log files.
Mitigations (5)
ImplementationThe 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.
ImplementationWhen 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 DesignLimit the interleaving of operations on files from multiple processes.
Implementation, Architecture and DesignIf 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.
ImplementationRecheck the resource after the use call to verify that the action was taken appropriately.
Examples (2)
The following code checks a file, then updates its contents.
struct stat *sb; ... lstat("...",sb); // it has not been updated since the last time it was read printf("stated file\n"); if (sb->st_mtimespec==...){ print("Now updating things\n"); updateThings(); }
Bad · C
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…
if(!access(file,W_OK)) { f = fopen(file,"w+"); operate(f); ... } else { fprintf(stderr,"Unable to open file %s.\n",file); }
Bad · C
CVE IDTitleCVSSSeverityPublished
CVE-2024-43067 Time-of-check Time-of-use (TOCTOU) Race Condition in Camera — Snapdragon 7.8 High2025-04-07
CVE-2024-54084 SMM Arbitrary Write via TOCTOU Vulnerability — AptioV 7.5 High2025-03-11
CVE-2024-53694 QVPN Device Client, Qsync, Qfinder Pro — QVPN Device Client for Mac 7.0 -2025-03-07
CVE-2024-53032 Time-of-check Time-of-use (TOCTOU) Race Condition in Automotive OS Platform — Snapdragon 7.8 High2025-03-03
CVE-2024-53028 Time-of-check Time-of-use (TOCTOU) Race Condition in Automotive Vehicle Networks — Snapdragon 7.8 High2025-03-03
CVE-2025-0759 IBM EntireX race condition — EntireX 3.3 Low2025-02-27
CVE-2025-26620 Duende.AccessTokenManagement race condition when concurrently retrieving customized Client Credentials Access Tokens — foss 5.9 -2025-02-18
CVE-2025-23359 NVIDIA Container Toolkit 安全漏洞 — Container Toolkit 8.3 High2025-02-12
CVE-2025-24036 Microsoft AutoUpdate (MAU) Elevation of Privilege Vulnerability — Microsoft AutoUpdate for Mac 7.0 High2025-02-11
CVE-2025-24432 Adobe Commerce | Time-of-check Time-of-use (TOCTOU) Race Condition (CWE-367) — Adobe Commerce 3.7 Low2025-02-11
CVE-2025-24430 Adobe Commerce | Time-of-check Time-of-use (TOCTOU) Race Condition (CWE-367) — Adobe Commerce 3.7 Low2025-02-11
CVE-2024-45560 Time-of-check Time-of-use (TOCTOU) Race Condition in Camera — Snapdragon 7.8 High2025-02-03
CVE-2024-38418 Time-of-check Time-of-use (TOCTOU) Race Condition in Camera Linux — Snapdragon 7.8 High2025-02-03
CVE-2025-22394 Dell Display Manager 安全漏洞 — Dell Display Manager 6.7 Medium2025-01-15
CVE-2024-42444 TOCTOU Race Condition between DMA and SMM — AptioV 7.5 High2025-01-14
CVE-2024-41787 IBM Engineering Requirements Management DOORS Next code execution — Engineering Requirements Management DOORS Next 9.8 Critical2025-01-10
CVE-2024-56337 Apache Tomcat: RCE due to TOCTOU issue in JSP compilation - CVE-2024-50379 mitigation was incomplete — Apache Tomcat 8.1 -2024-12-20
CVE-2024-50379 Apache Tomcat: RCE due to TOCTOU issue in JSP compilation — Apache Tomcat 8.1 -2024-12-17
CVE-2024-10972 WinPmem Improper Input Validation vulnerability — WinPmem 7.3 High2024-12-16
CVE-2024-53289 Dell ThinOS 安全漏洞 — Wyse Proprietary OS (Modern ThinOS) 7.8 High2024-12-11
CVE-2024-27134 Excessive directory permissions in MLflow leads to local privilege escalation when using spark_udf 7.0 High2024-11-25
CVE-2024-41779 IBM Engineering Systems Design Rhapsody - Model Manager — Engineering Systems Design Rhapsody - Model Manager 9.8 Critical2024-11-22
CVE-2024-49046 Windows Win32 Kernel Subsystem Elevation of Privilege Vulnerability — Windows 10 Version 1809 7.8 High2024-11-12
CVE-2024-43452 Windows Registry Elevation of Privilege Vulnerability — Windows 10 Version 1809 7.5 High2024-11-12
CVE-2024-51563 bhyve(8) virtio_vq_recordon time-of-check to time-of-use race — FreeBSD 7.0AIHighAI2024-11-12
CVE-2024-50592 Local Privilege Escalation via Race Condition — Elefant Software Updater 6.4 -2024-11-08
CVE-2024-38407 Time-of-check Time-of-use (TOCTOU) Race Condition in Camera — Snapdragon 7.8 High2024-11-04
CVE-2024-38406 Time-of-check Time-of-use (TOCTOU) Race Condition in Camera — Snapdragon 7.8 High2024-11-04
CVE-2024-49768 Waitress has request processing race condition in HTTP pipelining with invalid first request — waitress 9.1 Critical2024-10-29
CVE-2024-47494 Junos OS: Due to a race condition AgentD process causes a memory corruption and FPC reset — Junos OS 5.9 Medium2024-10-11

Vulnerabilities classified as CWE-367 (检查时间与使用时间(TOCTOU)的竞争条件) represent 325 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.