CWE-382 Variante Brouillon

J2EE Bad Practices: Use of System.exit()

This vulnerability occurs when a J2EE application directly calls System.exit(), which forcibly terminates the entire application server process, not just the application itself.

Définition

What is CWE-382?

This vulnerability occurs when a J2EE application directly calls System.exit(), which forcibly terminates the entire application server process, not just the application itself.
Calling System.exit() from within a deployed J2EE application is a dangerous anti-pattern. It grants a single application the power to shut down the shared container, crashing every other application and service running on the same server. This creates a severe reliability issue and an immediate vector for Denial-of-Service (DoS) attacks, as even an unprivileged user might trigger a code path that calls this method. Instead of using System.exit(), applications should manage their lifecycle gracefully through the container's administrative interfaces. Error conditions should be handled using exception mechanisms that log the issue and return an appropriate error response to the user, allowing the container and other co-hosted applications to continue running normally. This approach maintains system stability and aligns with the managed, multi-application environment that J2EE containers are designed to provide.
Impact réel

Real-world CVEs caused by CWE-382

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

    Identifier un chemin de code qui traite des entrées non fiables sans validation.

  2. 2

    Élaborer une charge utile qui exploite le comportement non sécurisé — injection, traversal, débordement ou abus de logique.

  3. 3

    Délivrer la charge utile via une requête normale et observer la réaction de l'application.

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

Included in the doPost() method defined below is a call to System.exit() in the event of a specific exception.

Vulnérable Java 
Public void doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
  	try {
  		...
  	} catch (ApplicationSpecificException ase) {
  		logger.error("Caught: " + ase.toString());
  		System.exit(1);
  	}
  }
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-382

  • Architecture and Design The shutdown function should be a privileged function available only to a properly authorized administrative user
  • Implementation Web applications should not call methods that cause the virtual machine to exit, such as System.exit()
  • Implementation Web applications should also not throw any Throwables to the application server as this may adversely affect the container.
  • Implementation Non-web applications may have a main() method that contains a System.exit(), but generally should not call System.exit() from other locations in the code
Signaux de détection

How to detect CWE-382

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

Correction automatique Plexicus

Plexicus détecte automatiquement CWE-382 et ouvre une PR de correction en moins de 60 secondes.

Codex Remedium analyse chaque commit, identifie cette faiblesse précise et livre une pull request prête à être relue avec le correctif. Pas de tickets. Pas de transferts.

Obtenir une démo Essayer Plexicus gratuitement
Questions fréquentes

Frequently asked questions

Qu'est-ce que CWE-382 ?

This vulnerability occurs when a J2EE application directly calls System.exit(), which forcibly terminates the entire application server process, not just the application itself.

Quelle est la gravité de CWE-382 ?

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-382 ?

MITRE lists the following affected platforms: Java.

Comment puis-je prévenir CWE-382 ?

The shutdown function should be a privileged function available only to a properly authorized administrative user Web applications should not call methods that cause the virtual machine to exit, such as System.exit()

Comment Plexicus détecte et corrige CWE-382 ?

Le moteur SAST de Plexicus reconnaît la signature de flux de données de CWE-382 à 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-382 ?

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

Faiblesses associées

Weaknesses related to CWE-382

CWE-705 Parent

Incorrect Control Flow Scoping

This vulnerability occurs when a program fails to return execution to the correct point in the code after finishing a specific operation…

CWE-248 Frère

Uncaught Exception

This vulnerability occurs when a function throws an error or exception, but the calling code does not have a proper handler to catch and…

CWE-395 Frère

Use of NullPointerException Catch to Detect NULL Pointer Dereference

Using a try-catch block for NullPointerException as a substitute for proper null checks is an anti-pattern. This approach masks the root…

CWE-396 Frère

Declaration of Catch for Generic Exception

This weakness occurs when code catches a generic exception type like 'Exception' or 'Throwable', which can hide specific errors and create…

CWE-397 Frère

Declaration of Throws for Generic Exception

This vulnerability occurs when a method is declared to throw an overly broad exception type, such as a generic 'Exception' or 'Throwable'.…

CWE-455 Frère

Non-exit on Failed Initialization

This vulnerability occurs when software continues to run as normal after encountering a critical security failure during its startup…

CWE-584 Frère

Return Inside Finally Block

This vulnerability occurs when a function places a return statement inside a finally block. This dangerous pattern silently discards any…

CWE-698 Frère

Execution After Redirect (EAR)

Execution After Redirect (EAR) occurs when a web application sends a redirect response to a user's browser but continues to run…

Ressources

Further reading

Prêt quand vous l'êtes

Arrêtez de payer par développeur.
Commencez à fermer la boucle.

Plexicus est l'ASPM natif IA qui scanne, filtre, corrige, penteste et explique — de façon autonome. Développeurs illimités, dépôts illimités, actions IA à usage équitable. Vrai niveau gratuit, €269/mo annuel quand vous êtes prêt.

Commencer gratuitement Réserver une démo