CWE-396: Declaration of Catch for Generic Exception

Definition

What is CWE-396?

This weakness occurs when code catches a generic exception type like 'Exception' or 'Throwable', which can hide specific errors and create insecure error handling logic.

While it may seem cleaner to catch a broad exception like 'Exception' instead of writing multiple specific catch blocks, this practice is risky. It masks the true nature of errors, preventing you from handling different failure scenarios appropriately. Exceptions that deserve special recovery logic, or that shouldn't be caught at that point in the program, get lumped together and ignored. As your application evolves and starts throwing new, more specific exception types, this broad catch will silently swallow them all. This defeats the core purpose of a typed exception system, making your code less robust and secure over time. It often leads to complex, bug-prone error handling that can introduce vulnerabilities, as critical failures go unnoticed and unlogged.

Real-world impact

Real-world CVEs caused by CWE-396

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

How attackers exploit it

Step-by-step attacker path

1
The following code excerpt handles three types of exceptions in an identical fashion.
2
At first blush, it may seem preferable to deal with these exceptions in a single catch block, as follows:
3
However, if doExchange() is modified to throw a new type of exception that should be handled in some different kind of way, the broad catch block will prevent the compiler from pointing out the situation. Further, the new catch block will now also handle exceptions derived from RuntimeException such as ClassCastException, and NullPointerException, which is not the programmer's intent.

Vulnerable code example

Vulnerable Java

At first blush, it may seem preferable to deal with these exceptions in a single catch block, as follows:

Vulnerable Java

try {
  	doExchange();
  }
  catch (Exception e) {
  	logger.error("doExchange failed", e);
  }

Secure code example

Secure Java

The following code excerpt handles three types of exceptions in an identical fashion.

Secure Java

try {
  	doExchange();
  }
  catch (IOException e) {
  	logger.error("doExchange failed", e);
  }
  catch (InvocationTargetException e) {
  		logger.error("doExchange failed", e);
  }
  catch (SQLException e) {
  		logger.error("doExchange failed", e);
  }

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-396

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-396

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-396

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

Frequently asked questions

What is CWE-396?

This weakness occurs when code catches a generic exception type like 'Exception' or 'Throwable', which can hide specific errors and create insecure error handling logic.

How serious is CWE-396?

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

MITRE lists the following affected platforms: C++, Java, C#, Python.

How can I prevent CWE-396?

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

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

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

Related weaknesses

Weaknesses related to CWE-396

CWE-705 Parent

Ready to validate what matters?

Plexicus is Proof-Driven AppSec: validated findings, contextual understanding, and reviewed remediation — anchored in evidence, scoped with you.

Request AI Swarm Pentest

Declaration of Catch for Generic Exception

What is CWE-396?

Real-world CVEs caused by CWE-396

Step-by-step attacker path

Vulnerable Java

Secure Java

How to prevent CWE-396

How to detect CWE-396

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

Frequently asked questions

Weaknesses related to CWE-396

Incorrect Control Flow Scoping

Uncaught Exception

J2EE Bad Practices: Use of System.exit()

Use of NullPointerException Catch to Detect NULL Pointer Dereference

Declaration of Throws for Generic Exception

Non-exit on Failed Initialization

Return Inside Finally Block

Execution After Redirect (EAR)

Further reading

Ready to validate what matters?

Check whether AI Swarm Pentest fits your environment.

Request received. Book the next step.

Sample evidence handover

Server-Side Request Forgery in `webhooks/receiver`