CWE-460: Improper Cleanup on Thrown Exception

Base Draft Simple

CWE版本: 4.18

更新日期: 2025-09-09

弱点描述

The product does not clean up its state or incorrectly cleans up its state when an exception is thrown, leading to unexpected state or control flow.

扩展描述

Often, when functions or loops become complicated, some level of resource cleanup is needed throughout execution. Exceptions can disturb the flow of the code and prevent the necessary cleanup from happening.

常见后果

影响范围: Other

技术影响: Varies by Context

说明: The code could be left in a bad state.

潜在缓解措施

阶段: Implementation

描述: If one breaks from a loop or function by throwing an exception, make sure that cleanup happens or that you should exit the program. Use throwing exceptions sparsely.

检测方法

方法: 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.)

有效性: High

引入模式

阶段 说明
Implementation REALIZATION: This weakness is caused during implementation of an architectural security tactic.

适用平台

编程语言
C (Undetermined) C++ (Undetermined) Java (Undetermined) C# (Undetermined)

分类映射

分类名称 条目ID 条目名称 映射适配度
CLASP - Improper cleanup on thrown exception -
The CERT Oracle Secure Coding Standard for Java (2011) ERR03-J Restore prior object state on method failure -
The CERT Oracle Secure Coding Standard for Java (2011) ERR05-J Do not let checked exceptions escape from a finally block -
SEI CERT Perl Coding Standard EXP31-PL Do not suppress or ignore exceptions Imprecise
关键信息

CWE ID: CWE-460

抽象级别: Base

结构: Simple

状态: Draft

利用可能性: Medium

相关弱点