COMMON WEAKNESS ENUMERATIONDraft

CWE-248

Uncaught Exception

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

Soyutlama

Base

Yapı

Simple

Sömürü İhtimali

Medium

Problemi anla

Problem nedir?

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

Genişletilmiş açıklama

When an exception is not caught, it may cause the program to crash or expose sensitive information.

Kök neden

Problem nasıl ve ne zaman oluşur?

Yaşam döngüsü evresi

Implementation

Risk

Başarılı sömürü neye yol açar?

DoS: Crash, Exit, or RestartRead Application Data

Etkilenen güvenlik alanları: Availability, Confidentiality

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.

Savunma

Nasıl önlenir ve çözülür?

  • Follow secure coding guidelines for input handling and boundary checking.
  • Enforce strict security reviews and automated static analysis (SAST) checks.

Doğrulama

Nasıl tespit edilir?

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-248: Common Weakness Enumeration Entry CWE-248 · DayBreach Sözlük · DayBreach