CWE-383 J2EE Bad Practices: Direct Use of Threads

Thread management in a Web application is forbidden in some circumstances and is always highly error prone.

• Other: Quality Degradation, Varies by Context — Even without interfering with the container, thread management usually leads to bugs that are hard to detect and diagnose, such as deadlock, race conditions, and other synchronization errors.

• [Architecture and Design] For EJB, use framework approaches for parallel execution, instead of using threads.

• 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.)