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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

561 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, 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.
Mitigations (5)
Implementation 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.
Implementation 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.
Implementation Recheck 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 ID Title CVSS Severity Published
CVE-2023-35378 Windows Projected File System Elevation of Privilege Vulnerability — Windows 10 Version 1809 7.0 High 2023-08-08
CVE-2023-28576 Time-of-check Time-of-use (TOCTOU) Race Condition in Camera Kernel Driver — Snapdragon 6.4 Medium 2023-08-08
CVE-2023-35311 Microsoft Outlook Security Feature Bypass Vulnerability — Microsoft 365 Apps for Enterprise 8.8 High 2023-07-11
CVE-2023-33156 Microsoft Defender Elevation of Privilege Vulnerability — Microsoft Malware Protection Engine 6.3 Medium 2023-07-11
CVE-2023-33154 Windows Partition Management Driver Elevation of Privilege Vulnerability — Windows 10 Version 1809 7.8 High 2023-07-11
CVE-2023-1295 Privilege escalation with IO_RING_OP_CLOSE in the Linux Kernel — Linux Kernel 7.8 High 2023-06-28
CVE-2022-4149 Local privilege escalation using log file — Netskope Client 7.0 High 2023-06-15
CVE-2023-29337 NuGet Client Remote Code Execution Vulnerability — NuGet 6.2.3 7.1 High 2023-06-14
CVE-2023-2007 DPT I2O Controller driver 安全漏洞 — Linux kernel's DPT I2O Controller driver 7.8 - 2023-04-24
CVE-2023-1586 AVG Technologies AVG Antivirus 安全漏洞 — Avast Antivirus 6.5 Medium 2023-04-19
CVE-2023-1585 AVG Technologies AVG Antivirus 安全漏洞 — Avast Antivirus 6.5 Medium 2023-04-19
CVE-2023-0006 GlobalProtect App: Local File Deletion Vulnerability — GlobalProtect app 6.3 Medium 2023-04-12
CVE-2022-33270 Time-of-check time-of-use race condition in Modem — Snapdragon 7.5 High 2023-04-04
CVE-2022-3093 Tesla 安全漏洞 — Model 3 6.4 - 2023-03-29
CVE-2022-36980 Ivanti Avalanche 安全漏洞 — Avalanche 9.8 - 2023-03-29
CVE-2023-0778 Podman 安全漏洞 — podman 6.8 - 2023-03-27
CVE-2023-22883 Local Privilege Escalation in Zoom for Windows Installers — Zoom Client for Meetings for IT Admin Windows installers 7.2 High 2023-03-16
CVE-2023-24861 Windows Graphics Component Elevation of Privilege Vulnerability — Windows 10 Version 1809 7.0 High 2023-03-14
CVE-2023-23389 Microsoft Defender Elevation of Privilege Vulnerability — Microsoft Malware Protection Engine 6.3 Medium 2023-03-14
CVE-2022-33257 Time-of-check time-of-use race condition in Core — Snapdragon 9.3 Critical 2023-03-07
CVE-2022-34398 Dell BIOS 安全漏洞 — CPG BIOS 7.5 High 2023-02-01
CVE-2023-21555 Windows Layer 2 Tunneling Protocol (L2TP) Remote Code Execution Vulnerability — Windows 10 Version 1809 8.1 High 2023-01-10
CVE-2023-21537 Microsoft Message Queuing (MSMQ) Elevation of Privilege Vulnerability — Windows 10 Version 1809 7.8 High 2023-01-10
CVE-2022-36927 Local Privilege Escalation in Zoom Rooms for macOS Clients — Zoom Rooms for macOS 8.8 High 2023-01-09
CVE-2022-36929 Local Privilege Escalation in Zoom Rooms for Windows Clients — Zoom Rooms for Windows 7.8 High 2023-01-09
CVE-2022-39908 SAMSUNG Mobile devices 安全漏洞 — Samsung Mobile Devices 6.9 Medium 2022-12-08
CVE-2022-45842 WordPress WP ULike Plugin <= 4.6.4 is vulnerable to Race Condition vulnerability — WP ULike (WordPress plugin) 5.3 Medium 2022-11-30
CVE-2022-22220 Junos OS and Junos OS Evolved: Due to a race condition the rpd process can crash upon receipt of a BGP update message containing flow spec route — Junos OS 5.9 Medium 2022-10-18
CVE-2022-29800 networkd-dispatcher 安全漏洞 — networkd-dispatcher 4.7 - 2022-09-21
CVE-2022-26859 Dell BIOS 安全漏洞 — CPG BIOS 6.1 Medium 2022-09-06

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