CWE-383
Weakness AllowedJ2EE Bad Practices: Direct Use of Threads
Abstraction: Variant · Status: Draft
Thread management in a Web application is forbidden in some circumstances and is always highly error prone.
Mapping guidance
This CWE entry is at the Variant level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.
Modes of introduction
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.)
Effectiveness: High
Content history
added/updated demonstrative examples
updated Time_of_Introduction
updated Relationships, Other_Notes, Taxonomy_Mappings
updated Description, Other_Notes, Relationships
updated Common_Consequences
updated Common_Consequences
updated Relationships
updated Potential_Mitigations
updated Relationships, Taxonomy_Mappings
updated Relationships
updated References, Relationships
updated Detection_Factors, Relationships, Time_of_Introduction
updated Mapping_Notes
updated Applicable_Platforms, Weakness_Ordinalities
updated Background_Details, Common_Consequences, Description, References
0 vulnerabilities reference this CWE, most recent first.
No vulnerabilities reference this CWE.
Mitigation
For EJB, use framework approaches for parallel execution, instead of using threads.
No CAPEC attack patterns related to this CWE.