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.

Potential Impact

Demonstrative Examples

int foo = 0;int storenum(int num) {static int counter = 0;counter++;if (num > foo) foo = num;return foo;}

public classRace {
                        static int foo = 0;public static void main() {
                              
                                 new Threader().start();foo = 1;
                           }public static class Threader extends Thread {
                              
                                 public void run() {System.out.println(foo);}
                           }
                     }

Mitigations & Prevention

Detection Methods

• Automated Static Analysis High — Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then sea

Real-World CVE Examples

Related Weaknesses

Taxonomy Mappings

• CLASP: — Race condition within a thread
• CERT C Secure Coding: CON32-C — Prevent data races when accessing bit-fields from multiple threads
• CERT C Secure Coding: CON40-C — Do not refer to an atomic variable twice in an expression
• CERT C Secure Coding: CON43-C — Do not allow data races in multithreaded code
• The CERT Oracle Secure Coding Standard for Java (2011): VNA02-J — Ensure that compound operations on shared variables are atomic
• The CERT Oracle Secure Coding Standard for Java (2011): VNA03-J — Do not assume that a group of calls to independently atomic methods is atomic
• Software Fault Patterns: SFP19 — Missing Lock