CWEweakness
CWE-584 Return Inside Finally Block
- Abstraction
- Base
- Structure
- Simple
- Status
- Draft
- Languages
- Not Language-Specific, Python
- CWE version
- 5.0
Description
The code has a return statement inside a finally block.
Common consequences
• Other: Alter Execution Logic, Unexpected State, Varies by Context — With some languages, this will cause any thrown exception in the try block to be discarded.
Potential mitigations
• [Implementation] Do not use a return statement inside the finally block. The finally block should have "cleanup" code.
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 (1)
- CWE-705 Incorrect Control Flow Scoping weakness