Standardlikelihood: Highseverity: HighDraft
CAPEC-29Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions
Abstraction
Standard
Status
Draft
Likelihood
High
Severity
High
Description
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.
Related weaknesses· 9
Related attack patterns· 1
Exploits9
| Type | Target | Confidence | Tier |
|---|---|---|---|
| Weakness | Improper Synchronizationcwe-662 | 100% | live |
| Weakness | Use of a Non-reentrant Function in a Concurrent Contextcwe-663 | 100% | live |
| Weakness | Insufficient Control Flow Managementcwe-691 | 100% | live |
| Weakness | Race Condition within a Threadcwe-366 | 100% | live |
| Weakness | Time-of-check Time-of-use (TOCTOU) Race Conditioncwe-367 | 100% | live |
| Weakness | Improper Initializationcwe-665 | 100% | live |
| Weakness | Context Switching Race Conditioncwe-368 | 100% | live |
| Weakness | Missing Check for Certificate Revocation after Initial Checkcwe-370 | 100% | live |
| Weakness | Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')cwe-362 | 100% | live |
Related by meaning· 6
Nearest entities by semantic similarity across the cs-graph corpus.