CWE-383: J2EE Bad Practices: Direct Use of Threads
CWE版本: 4.18
更新日期: 2025-09-09
弱点描述
Thread management in a Web application is forbidden in some circumstances and is always highly error prone.
扩展描述
Thread management in a web application is forbidden by the J2EE standard in some circumstances and is always highly error prone. Managing threads is difficult and is likely to interfere in unpredictable ways with the behavior of the application container. Even without interfering with the container, thread management usually leads to bugs that are hard to detect and diagnose like deadlock, race conditions, and other synchronization errors.
常见后果
影响范围: Other
技术影响: Quality Degradation
潜在缓解措施
阶段: 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.)
有效性: High
引入模式
| 阶段 | 说明 |
|---|---|
| Implementation | - |
适用平台
编程语言
分类映射
| 分类名称 | 条目ID | 条目名称 | 映射适配度 |
|---|---|---|---|
| 7 Pernicious Kingdoms | - | J2EE Bad Practices: Threads | - |
| Software Fault Patterns | SFP3 | Use of an improper API | - |