Skip to content
OpenAdvisories

Weakness (CWE)

CWE-248: Uncaught Exception

Base Draft

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

How to prevent it (3 mitigations)

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

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

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

Source: MITRE CWE-248

All Critical High Medium Low Exploited only Public exploit

1 result · Clear filters · Feed

  • Low 2.4
    CVE-2026-55780 Public exploit

    NanaZip: Uncaught exception / unbounded allocation in NanaZip .NET single-file Extract() via unvalidated entry Size

    NanaZip is the 7-Zip derivative intended for the modern Windows experience. Prior to 6.5.1749.0, NanaZip's .NET single-file bundle handler in NanaZip.Codecs.Archive.DotNetSingleFile.cpp sizes its extraction buffer from the bundle entry Size field, which is on…

    M2Team NanaZip