CAPEC-26: Leveraging Race Conditions

ID CAPEC-26
Typical Severity High
Likelihood Of Attack High
Status Stable

The adversary targets a race condition occurring when multiple processes access and manipulate the same resource concurrently, and the outcome of the execution depends on the particular order in which the access takes place. The adversary can leverage a race condition by "running the race", modifying the resource and modifying the normal execution flow. For instance, a race condition can occur while accessing a file: the adversary can trick the system by replacing the original file with their version and cause the system to read the malicious file.

https://capec.mitre.org/data/definitions/26.html

Weaknesses

# ID Name Type
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') weakness
CWE-363 Race Condition Enabling Link Following weakness
CWE-366 Race Condition within a Thread weakness
CWE-368 Context Switching Race Condition weakness
CWE-370 Missing Check for Certificate Revocation after Initial Check weakness
CWE-662 Improper Synchronization weakness
CWE-665 Improper Initialization weakness
CWE-667 Improper Locking weakness
CWE-689 Permission Race Condition During Resource Copy weakness
CWE-1223 Race Condition for Write-Once Attributes weakness
CWE-1254 Incorrect Comparison Logic Granularity weakness
CWE-1298 Hardware Logic Contains Race Conditions weakness
Loading...