CWE-536 Variant Incomplete

Servlet Runtime Error Message Containing Sensitive Information

This vulnerability occurs when a Java servlet application displays detailed runtime error messages that reveal sensitive information about the application's internal structure, such as stack traces,…

Definition

What is CWE-536?

This vulnerability occurs when a Java servlet application displays detailed runtime error messages that reveal sensitive information about the application's internal structure, such as stack traces, file paths, or database queries. These unhandled exception details can give attackers critical insights to craft further exploits.
When an uncaught exception occurs in a servlet, the default error pages or overly verbose logging often dump the full stack trace and error context directly into the HTTP response. This information is gold for an attacker, as it can expose underlying technologies, framework versions, SQL query structures, internal file system paths, and even snippets of your business logic. It essentially provides a roadmap of your application's weaknesses and internal architecture. To prevent this, you should implement a global error handler that catches all unhandled exceptions and returns a generic, user-friendly error message to the client, while logging the detailed diagnostic information securely on the server side. Always ensure your application is deployed in production mode, which typically suppresses verbose debugging output, and regularly test error conditions to verify no sensitive data leaks through these channels.
Real-world impact

Real-world CVEs caused by CWE-536

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

The following servlet code does not catch runtime exceptions, meaning that if such an exception were to occur, the container may display potentially dangerous information (such as a full stack trace).

Vulnerable Java 
public void doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
  		String username = request.getParameter("username");
```
// May cause unchecked NullPointerException.* 
  		if (username.length() < 10) {
  		```
  			...
  		}
  }
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-536

  • Architecture Use safe-by-default frameworks and APIs that prevent the unsafe pattern from being expressible.
  • Implementation Validate input at trust boundaries; use allowlists, not denylists.
  • Implementation Apply the principle of least privilege to credentials, file paths, and runtime permissions.
  • Testing Cover this weakness in CI: SAST rules + targeted unit tests for the data flow.
  • Operation Monitor logs for the runtime signals listed in the next section.
Detection signals

How to detect CWE-536

SAST High

Run static analysis (SAST) on the codebase looking for the unsafe pattern in the data flow.

DAST Moderate

Run dynamic application security testing against the live endpoint.

Runtime Moderate

Watch runtime logs for unusual exception traces, malformed input, or authorization bypass attempts.

Code review Moderate

Code review: flag any new code that handles input from this surface without using the validated framework helpers.

Plexicus auto-fix

Plexicus auto-detects CWE-536 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-536?

This vulnerability occurs when a Java servlet application displays detailed runtime error messages that reveal sensitive information about the application's internal structure, such as stack traces, file paths, or database queries. These unhandled exception details can give attackers critical insights to craft further exploits.

How serious is CWE-536?

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

MITRE has not specified affected platforms for this CWE — it can apply across most application stacks.

How can I prevent CWE-536?

Use safe-by-default frameworks, validate untrusted input at trust boundaries, and apply the principle of least privilege. Cover the data-flow signature in CI with SAST.

How does Plexicus detect and fix CWE-536?

Plexicus's SAST engine matches the data-flow signature for CWE-536 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-536?

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

Related weaknesses

Weaknesses related to CWE-536

CWE-211 Parent

Externally-Generated Error Message Containing Sensitive Information

This vulnerability occurs when an application triggers an error message from an external component—like a database, interpreter, or…

CWE-535 Sibling

Exposure of Information Through Shell Error Message

This vulnerability occurs when a web application's command shell returns detailed error messages to users. Attackers can analyze these…

CWE-537 Sibling

Java Runtime Error Message Containing Sensitive Information

This vulnerability occurs when a Java application's runtime error messages reveal sensitive details about the system, such as file paths,…

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.

Get started free Book a demo