This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit

Unsafe Mobile Code: Public finalize() Method

Revision as of 17:23, 21 July 2006 by Weilin Zhong (talk | contribs) (Moved the definition of mobile code and its security concern to :Category:Unsafe Mobile Code)

Jump to: navigation, search

This is a Vulnerability. To view all vulnerabilities, please see the Vulnerability Category page.

This article includes content generously donated to OWASP by MicroFocus Logo.png


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 finialize(). 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. If you are using finalize() as it was designed, there is no reason to declare finalize() with anything other than protected access.

For more details about mobile code and its security concerns, please see Category:Unsafe Mobile Code.


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

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

Related Threats

Related Attacks

Related Vulnerabilities

Related Countermeasures