CWE-366: Race Condition within a Thread

Description

If two threads of execution use a resource simultaneously, there exists the possibility that resources may be used while invalid, in turn making the state of execution undefined.

Abstraction: BaseA weakness specific enough to point to detection and prevention methods.
Likelihood of exploit: Medium
Status: Draft

Common consequences

IntegrityOther
Alter Execution Logic; Unexpected State
The main problem is that -- if a lock is overcome -- data could be altered in a bad state.

Potential mitigations

Architecture and Design
Use locking functionality. This is the recommended solution. Implement some form of locking mechanism around code which alters or reads persistent data in a multithreaded environment.
Architecture and Design
Create resource-locking validation checks. If no inherent locking mechanisms exist, use flags and signals to enforce your own blocking scheme when resources are being used by other threads of execution.

Related weaknesses

Parent weaknesses

CWE-362Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

CAPEC attack patterns that exploit it

Potential mitigations

Architecture and Design

Use locking functionality. This is the recommended solution. Implement some form of locking mechanism around code which alters or reads persistent data in a multithreaded environment.

Architecture and Design

Create resource-locking validation checks. If no inherent locking mechanisms exist, use flags and signals to enforce your own blocking scheme when resources are being used by other threads of execution.