CWE-383: J2EE Bad Practices: Direct Use of Threads

Extended Description

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.

Code Examples & CVEs

Demonstrative Examples

In the following example, a new Thread object is created and invoked directly from within the body of a doGet() method in a Java servlet.

BadJava

public void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {                                                                                 // Perform servlet tasks.                            ...                                                        // Create a new thread to handle background processing.                            Runnable r = new Runnable() {                               public void run() {                                                                                                                     // Process and store request statistics.                                        ...                                  }                            };                            new Thread(r).start();                      }

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-383 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-383, J2EE Bad Practices: Direct Use of Threads, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Address J2EE Bad Practices: Direct Use of Threads during Architecture and Design

MITRE associates mitigation with Architecture and Design; documented detection approaches include Automated Static Analysis; recorded impacts include Quality Degradation. Use these source-defined anchors to turn CWE-383 into implementation, review, and verification checks for the affected component.

CWE-383: J2EE Bad Practices: Direct Use of Threads — MITRE CWE

Triage CWE-383 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-383, J2EE Bad Practices: Direct Use of Threads, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-383

Apply MITRE's full root-cause mapping guidance when using CWE-383, J2EE Bad Practices: Direct Use of Threads. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping Guidance — MITRE CWE

Validate CWE-383 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-383, J2EE Bad Practices: Direct Use of Threads. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick Tips — MITRE CWE

Frequently Asked Questions

What is CWE-383: J2EE Bad Practices: Direct Use of Threads?+

CWE-383: J2EE Bad Practices: Direct Use of Threads is a Common Weakness Enumeration (CWE) entry maintained by MITRE. 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.

What are the security consequences of J2EE Bad Practices: Direct Use of Threads?+

If exploited, CWE-383 (J2EE Bad Practices: Direct Use of Threads) it can compromise Other, leading to outcomes such as Quality Degradation.

How do you prevent or mitigate J2EE Bad Practices: Direct Use of Threads?+

Recommended mitigations for CWE-383 include: For EJB, use framework approaches for parallel execution, instead of using threads.

Which programming languages are affected by J2EE Bad Practices: Direct Use of Threads?+

CWE-383 commonly affects Java. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-383 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

CWE-383: J2EE Bad Practices: Direct Use of Threads

Extended Description

Technical Details

Applicable To

Security Consequences

Scope

Impact

Mitigation Strategies

Phase

Description

Detection Methods