CWE-382 Variant Draft

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.

Definition

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.
Real-world impact

Real-world CVEs caused by CWE-382

No public CVE references are linked to this CWE in MITRE's catalog yet.

How attackers exploit it

Step-by-step attacker path

  1. 1

    Identify a code path that handles untrusted input without validation.

  2. 2

    Craft a payload that exercises the unsafe behavior — injection, traversal, overflow, or logic abuse.

  3. 3

    Deliver the payload through a normal request and observe the application's reaction.

  4. 4

    Iterate until the response leaks data, executes attacker code, or escalates privileges.

Vulnerable code example

Vulnerable Java

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

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

Secure pseudo

Secure 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.
Prevention checklist

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
Detection signals

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

Plexicus auto-fix

Plexicus auto-detects CWE-382 and opens a fix PR in under 60 seconds.

Codex Remedium scans every commit, identifies this exact weakness, and ships a reviewer-ready pull request with the patch. No tickets. No hand-offs.

Get a demo Try Plexicus free
Frequently asked questions

Frequently asked questions

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.

How serious is CWE-382?

MITRE has not published a likelihood-of-exploit rating for this weakness. Treat it as medium-impact until your threat model proves otherwise.

What languages or platforms are affected by CWE-382?

MITRE lists the following affected platforms: Java.

How can I prevent 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()

How does Plexicus detect and fix CWE-382?

Plexicus's SAST engine matches the data-flow signature for CWE-382 on every commit. When a match is found, our Codex Remedium agent opens a fix PR with the corrected code, tests, and a one-line summary for the reviewer.

Where can I learn more about CWE-382?

MITRE publishes the canonical definition at https://cwe.mitre.org/data/definitions/382.html. You can also reference OWASP and NIST documentation for adjacent guidance.

Related weaknesses

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 Sibling

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 Sibling

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 Sibling

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 Sibling

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 Sibling

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 Sibling

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 Sibling

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…

Resources

Further reading

Ready when you are

Don't Let Security
Weigh You Down.

Stop choosing between AI velocity and security debt. Plexicus is the only platform that runs Vibe Coding Security and ASPM in parallel — one workflow, every codebase.