COMMON WEAKNESS ENUMERATIONDraft

CWE-584

Return Inside Finally Block

The code has a return statement inside a finally block, which will cause any thrown exception in the try block to be discarded.

Abstraction

Base

Structure

Simple

Likelihood of Exploit

Medium

Understand the problem

What is the problem?

The code has a return statement inside a finally block, which will cause any thrown exception in the try block to be discarded.

Root cause

How and when does the problem arise?

Lifecycle phase

Implementation

Risk

What does successful exploitation lead to?

Alter Execution Logic

Affected security scopes: Other

Defence

How is it prevented and fixed?

Implementation

Implementation-phase defence

Detail
Do not use a return statement inside the finally block. The finally block should have "cleanup" code.

Verification

How is it detected?

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