CWE-383 Variante Brouillon

J2EE Bad Practices: Direct Use of Threads

Creating or managing threads directly within a J2EE application is a risky practice that violates the platform's standards and often leads to unstable applications.

Définition

What is CWE-383?

Creating or managing threads directly within a J2EE application is a risky practice that violates the platform's standards and often leads to unstable applications.

Direct thread management in a J2EE environment is problematic because it bypasses the container's control, which is designed to manage resources and concurrency. This can cause unpredictable conflicts with the application server's own threading, leading to crashes, performance issues, and difficult-to-reproduce errors. Common bugs like deadlocks and race conditions become much harder to diagnose when they originate from custom threads instead of the container-managed ones. These flaws are tricky to find manually, especially in complex deployments. While SAST tools can flag the pattern, Plexicus uses AI to analyze the context and suggest specific, safe refactoring steps—such as replacing custom threads with JMS or the ManagedExecutorService—saving significant development time and preventing runtime instability.

Impact réel

Real-world CVEs caused by CWE-383

Aucune référence CVE publique n'est liée à ce CWE dans le catalogue MITRE pour le moment.

Comment les attaquants l'exploitent

Parcours de l'attaquant étape par étape

1
Identifier un chemin de code qui traite des entrées non fiables sans validation.
2
Élaborer une charge utile qui exploite le comportement non sécurisé — injection, traversal, débordement ou abus de logique.
3
Délivrer la charge utile via une requête normale et observer la réaction de l'application.
4
Itérer jusqu'à ce que la réponse divulgue des données, exécute le code de l'attaquant ou élève les privilèges.

Exemple de code vulnérable

Vulnerable Java

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.

Vulnérable Java

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();}

Exemple de code sécurisé

Secure pseudo

Sécurisé pseudo

// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
  const safe = validateAndEscape(input);
  return executeWithGuards(safe);
}

What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.

Liste de contrôle de prévention

How to prevent CWE-383

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

Signaux de détection

How to detect CWE-383

Automated Static Analysis High

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

CWE-383

Don't catalog this weakness. Prove it's reachable.

Plexicus turns CWE catalogs into evidence: every CWE-pattern is matched against your real code graph, reach is proven on a sandbox clone, and verified findings ship as reviewed PRs.

Request AI Swarm Pentest

Questions fréquentes

Frequently asked questions

Qu'est-ce que CWE-383 ?

Creating or managing threads directly within a J2EE application is a risky practice that violates the platform's standards and often leads to unstable applications.

Quelle est la gravité de CWE-383 ?

MITRE n'a pas publié de note de probabilité d'exploitation pour cette faiblesse. Traitez-la comme un impact moyen jusqu'à ce que votre modèle de menace prouve le contraire.

Quels langages ou plateformes sont affectés par CWE-383 ?

MITRE lists the following affected platforms: Java.

Comment puis-je prévenir CWE-383 ?

For EJB, use framework approaches for parallel execution, instead of using threads.

Comment Plexicus détecte et corrige CWE-383 ?

Le moteur SAST de Plexicus reconnaît la signature de flux de données de CWE-383 à chaque commit. Lorsqu'une correspondance est trouvée, notre agent Codex Remedium ouvre une PR de correction avec le code corrigé, les tests et un résumé d'une ligne pour le relecteur.

Où puis-je en savoir plus sur CWE-383 ?

MITRE publie la définition canonique à https://cwe.mitre.org/data/definitions/383.html. Vous pouvez également consulter la documentation OWASP et NIST pour des conseils adjacents.

Faiblesses associées

Weaknesses related to CWE-383

CWE-695 Parent

Prêt à valider ce qui compte.

Plexicus est Proof-Driven AppSec : findings validés, compréhension contextuelle et remédiation relue — ancrée dans la preuve, scopée avec vous.

Réserver un Pentest

J2EE Bad Practices: Direct Use of Threads

What is CWE-383?

Real-world CVEs caused by CWE-383

Parcours de l'attaquant étape par étape

Vulnerable Java

Secure pseudo

How to prevent CWE-383

How to detect CWE-383

Don't catalog this weakness. Prove it's reachable.

Frequently asked questions

Weaknesses related to CWE-383

Use of Low-Level Functionality

Direct Use of Unsafe JNI

J2EE Bad Practices: Direct Management of Connections

J2EE Bad Practices: Direct Use of Sockets

EJB Bad Practices: Use of Synchronization Primitives

EJB Bad Practices: Use of AWT Swing

EJB Bad Practices: Use of Java I/O

Further reading

Prêt à valider ce qui compte.

Vérifiez si l'AI Swarm Pentest convient à votre environnement.

Demande reçue. Réservez la prochaine étape.

Sample evidence handover

Server-Side Request Forgery in `webhooks/receiver`