CWE-586: Explicit Call to Finalize()
CWE版本: 4.18
更新日期: 2025-09-09
弱点描述
The product makes an explicit call to the finalize() method from outside the finalizer.
扩展描述
While the Java Language Specification allows an object's finalize() method to be called from outside the finalizer, doing so is usually a bad idea. For example, calling finalize() explicitly means that finalize() will be called more than once: the first time will be the explicit call and the last time will be the call that is made after the object is garbage collected.
常见后果
影响范围: Integrity Other
技术影响: Unexpected State Quality Degradation
潜在缓解措施
阶段: Implementation Testing
描述: Do not make explicit calls to finalize(). Use static analysis tools to spot such instances.
检测方法
方法: 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 | - |
适用平台
编程语言
分类映射
| 分类名称 | 条目ID | 条目名称 | 映射适配度 |
|---|---|---|---|
| The CERT Oracle Secure Coding Standard for Java (2011) | MET12-J | Do not use finalizers | - |
| Software Fault Patterns | SFP3 | Use of an improper API | - |