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

Difference between revisions of "Unsafe Mobile Code: Public finalize() Method"

Jump to: navigation, search
Line 1: Line 1:

Revision as of 17:48, 22 May 2009 Template:CandidateForDeletion

#REDIRECT Unsafe Mobile Code

Last revision (mm/dd/yy): 05/22/2009


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.

Risk Factors

  • Talk about the factors that make this vulnerability likely or unlikely to actually happen
  • Discuss the technical impact of a successful exploit of this vulnerability
  • Consider the likely [business impacts] of a successful attack


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

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

Related Attacks

Related Vulnerabilities

Related Controls

Related Technical Impacts