CWE-583 公开声明的finalize()方法

finalize() Method Declared Public

结构: Simple

Abstraction: Variant

状态: Incomplete

被利用可能性: unkown

基本描述

The program violates secure coding principles for mobile code by declaring a finalize() method public.

扩展描述

A program should never call finalize explicitly, except to call super.finalize() inside an implementation of finalize(). In mobile code situations, the otherwise error prone practice of manual garbage collection can become a security threat if an attacker can maliciously invoke one of your finalize() methods because it is declared with public access.

相关缺陷

  • cwe_Nature: ChildOf cwe_CWE_ID: 668 cwe_View_ID: 1000 cwe_Ordinal: Primary

适用平台

Language: {'cwe_Name': 'Java', 'cwe_Prevalence': 'Undetermined'}

常见的影响

范围 影响 注释
['Confidentiality', 'Integrity', 'Availability'] ['Alter Execution Logic', 'Execute Unauthorized Code or Commands', 'Modify Application Data']

可能的缓解方案

Implementation

策略:

If you are using finalize() as it was designed, there is no reason to declare finalize() with anything other than protected access.

示例代码

例

The following Java Applet code mistakenly declares a public finalize() method.

bad Java

public final class urlTool extends Applet {
public void finalize() {
...
}
...
}

Mobile code, in this case a Java Applet, is code that is transmitted across a network and executed on a remote machine. Because mobile code developers have little if any control of the environment in which their code will execute, special security concerns become relevant. One of the biggest environmental threats results from the risk that the mobile code will run side-by-side with other, potentially malicious, mobile code. Because all of the popular web browsers execute code from multiple sources together in the same JVM, many of the security guidelines for mobile code are focused on preventing manipulation of your objects' state and behavior by adversaries who have access to the same virtual machine where your program is running.

分类映射

映射的分类名 ImNode ID Fit Mapped Node Name
The CERT Oracle Secure Coding Standard for Java (2011) MET12-J Do not use finalizers
Software Fault Patterns SFP28 Unexpected access points