CWEweakness

CWE-397 Declaration of Throws for Generic Exception

Official page ↗
Abstraction
Base
Structure
Simple
Status
Draft
Languages
C#, C++, Java, Python
CWE version
5.0

Description

The product throws or raises an overly broad exception that can hide important details and produce inappropriate responses to certain conditions.

Common consequences

• Non-Repudiation, Other: Hide Activities, Alter Execution Logic — Declaring a method to throw Exception or Throwable promotes generic error handling procedures that make it difficult for callers to perform proper error handling and error recovery. For example, Java's exception mechanism makes it easy for callers to anticipate what can go wrong and write code to handle each specific exceptional circumstance. Throwing a generic exception can hide details about unexpected adversary activities by making it difficult to properly troubleshoot error conditions during execution.

Detection methods

• Automated Static Analysis: 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.)

Related

Child of · CWE (3)

  • CWE-221 Information Loss or Omission weakness
  • CWE-703 Improper Check or Handling of Exceptional Conditions weakness
  • CWE-705 Incorrect Control Flow Scoping weakness

Referenced by OWASP · mapped cwe (1)

  • A10:2025 Mishandling of Exceptional Conditions Top 10 2025