CWE-584
Weakness AllowedReturn Inside Finally Block
Abstraction: Base · Status: Draft
The code has a return statement inside a finally block.
Mapping guidance
This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.
Modes of introduction
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.)
Effectiveness: High
Content history
Submitted by members of the CWE community to extend early CWE versions
updated Potential_Mitigations, Time_of_Introduction
updated Relationships
updated Demonstrative_Examples
updated Common_Consequences, Relationships, Taxonomy_Mappings
updated Relationships, Taxonomy_Mappings
updated Potential_Mitigations
updated Relationships, Taxonomy_Mappings
updated Relationships, Taxonomy_Mappings
updated Detection_Factors, Relationships
updated Mapping_Notes
updated Applicable_Platforms, Weakness_Ordinalities
updated Applicable_Platforms, Common_Consequences, Description, References, Relationships, Taxonomy_Mappings
0 vulnerabilities reference this CWE, most recent first.
No vulnerabilities reference this CWE.
Mitigation
Do not use a return statement inside the finally block. The finally block should have "cleanup" code.
No CAPEC attack patterns related to this CWE.