CWEweakness

CWE-572 Call to Thread run() instead of start()

Official page ↗
Abstraction
Variant
Structure
Simple
Status
Draft
Languages
Java
CWE version
5.0

Description

The product calls a thread's run() method instead of calling start().

Common consequences

• Other: Quality Degradation, Varies by Context — The run() method will execute in the caller's thread of control, when the intention was likely to run in the thread of the callee.

Potential mitigations

• [Implementation] Use the start() method instead of the run() method.

Detection methods

• Automated Static Analysis: 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 searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)

Related

Child of · CWE (1)

  • CWE-821 Incorrect Synchronization weakness