CWE-382 Variante Rascunho

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.

Definição

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.

Impacto no mundo real

Real-world CVEs caused by CWE-382

Ainda não há referências CVE públicas associadas a este CWE no catálogo da MITRE.

Como os atacantes a exploram

Trajeto do atacante passo a passo

1
Identificar um caminho de código que trata input não confiável sem validação.
2
Criar um payload que explora o comportamento inseguro — injeção, traversal, overflow ou abuso de lógica.
3
Entregar o payload através de um pedido normal e observar a reação da aplicação.
4
Iterar até que a resposta exponha dados, execute código do atacante ou escale privilégios.

Exemplo de código vulnerável

Vulnerable Java

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

Vulnerável Java

Public void doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
  	try {
  		...
  	} catch (ApplicationSpecificException ase) {
  		logger.error("Caught: " + ase.toString());
  		System.exit(1);
  	}
  }

Exemplo de código seguro

Secure pseudo

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

Lista de verificação de prevenção

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

Sinais de deteção

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

CWE-382

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

Perguntas frequentes

Frequently asked questions

O que é o 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.

Qual a gravidade do CWE-382?

A MITRE não publicou uma classificação de probabilidade de exploração para esta fraqueza. Trate-a como impacto médio até o seu modelo de ameaças provar o contrário.

Que linguagens ou plataformas são afetadas pelo CWE-382?

MITRE lists the following affected platforms: Java.

Como posso prevenir o 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()

Como é que o Plexicus deteta e corrige o CWE-382?

O motor SAST do Plexicus correlaciona a assinatura de fluxo de dados do CWE-382 em cada commit. Quando é encontrada uma correspondência, o nosso agente Codex Remedium abre um PR de correção com o código corrigido, testes e um resumo de uma linha para o revisor.

Onde posso saber mais sobre o CWE-382?

A MITRE publica a definição canónica em https://cwe.mitre.org/data/definitions/382.html. Pode também consultar a documentação da OWASP e do NIST para orientações adjacentes.

Fraquezas relacionadas

Weaknesses related to CWE-382

CWE-705 Pai

Pronto para validar o que importa.

O Plexicus é Proof-Driven AppSec: achados validados, compreensão contextual e remediação revisada — ancorada em evidência, escopada com você.

Reservar Pentest

J2EE Bad Practices: Use of System.exit()

What is CWE-382?

Real-world CVEs caused by CWE-382

Trajeto do atacante passo a passo

Vulnerable Java

Secure pseudo

How to prevent CWE-382

How to detect CWE-382

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

Frequently asked questions

Weaknesses related to CWE-382

Incorrect Control Flow Scoping

Uncaught Exception

Use of NullPointerException Catch to Detect NULL Pointer Dereference

Declaration of Catch for Generic Exception

Declaration of Throws for Generic Exception

Non-exit on Failed Initialization

Return Inside Finally Block

Execution After Redirect (EAR)

Further reading

Pronto para validar o que importa.

Verifique se o AI Swarm Pentest se adequa ao seu ambiente.

Pedido recebido. Marque o próximo passo.

Sample evidence handover

Server-Side Request Forgery in `webhooks/receiver`