CWE-248Uncaught Exception

Description

An exception is thrown from a function, but it is not caught.

Common consequences

• Availability,Confidentiality→DoS: Crash, Exit, or Restart,Read Application Data
  An uncaught exception could cause the system to be placed in a state that could lead to a crash, exposure of sensitive information, or other unintended behaviors.

Potential mitigations

• Requirements
  The choice between a language which has named or unnamed exceptions needs to be done. While unnamed exceptions exacerbate the chance of not properly dealing with an exception, named exceptions suffer from the up call version of the weak base class problem.
• Requirements
  A language can be used which requires, at compile time, to catch all serious exceptions. However, one must make sure to use the most current version of the API as new exceptions could be added.
• Implementation
  Catch all relevant exceptions. This is the recommended solution. Ensure that all exceptions are handled in such a way that you can be sure of the state of your system at any given moment.

Related CWEs

Recent CVEs classified under this CWE