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

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

From OWASP
Jump to: navigation, search
(Moved the definition of mobile code and its security concern to :Category:Unsafe Mobile Code)
Line 2: Line 2:
 
{{Template:Fortify}}
 
{{Template:Fortify}}
  
−
==Abstract==
+
[[Category:FIXME|This is the text from the old template. This needs to be rewritten using the new template.]]
 +
 
 +
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
 +
 
 +
[[ASDR_TOC_Vulnerabilities|Vulnerabilities Table of Contents]]
 +
 
 +
[[ASDR Table of Contents]]
 +
__TOC__
  
−
The program violates secure coding principles for mobile code by declaring a finalize()method public.
 
  
 
==Description==
 
==Description==
 +
 +
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.
 
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.
Line 12: Line 20:
 
For more details about mobile code and its security concerns, please see [[:Category:Unsafe Mobile Code]].
 
For more details about mobile code and its security concerns, please see [[:Category:Unsafe Mobile Code]].
  
−
==Examples ==
+
 
 +
 
 +
==Risk Factors==
 +
 
 +
* Talk about the [[OWASP Risk Rating Methodology|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
 +
 
 +
 
 +
==Examples==
  
 
The following Java Applet code mistakenly declares a public finalize() method.
 
The following Java Applet code mistakenly declares a public finalize() method.
Line 26: Line 43:
 
</pre>
 
</pre>
  
−
==Related Threats==
 
  
−
==Related Attacks==
+
==Related [[Attacks]]==
  
−
==Related Vulnerabilities==
+
* [[Attack 1]]
 +
* [[Attack 2]]
  
−
==Related Countermeasures==
 
  
−
==Categories==
+
==Related [[Vulnerabilities]]==
  
 +
* [[Vulnerability 1]]
 +
* [[Vulnerabiltiy 2]]
 +
 +
 +
 +
==Related [[Controls]]==
 +
 +
* [[Control 1]]
 +
* [[Control 2]]
 +
 +
 +
==Related [[Technical Impacts]]==
 +
 +
* [[Technical Impact 1]]
 +
* [[Technical Impact 2]]
 +
 +
 +
==References==
 +
 +
TBD
 +
[[Category:FIXME|add links
 +
 +
In addition, one should classify vulnerability based on the following subcategories: Ex:<nowiki>[[Category:Error Handling Vulnerability]]</nowiki>
 +
 +
Availability Vulnerability
 +
 +
Authorization Vulnerability
 +
 +
Authentication Vulnerability
 +
 +
Concurrency Vulnerability
 +
 +
Configuration Vulnerability
 +
 +
Cryptographic Vulnerability
 +
 +
Encoding Vulnerability
 +
 +
Error Handling Vulnerability
 +
 +
Input Validation Vulnerability
 +
 +
Logging and Auditing Vulnerability
 +
 +
Session Management Vulnerability]]
 +
 +
__NOTOC__
 +
 +
 +
[[Category:OWASP ASDR Project]]
 
[[Category:Code Quality Vulnerability]]
 
[[Category:Code Quality Vulnerability]]
−
 
 
[[Category:Access Control Vulnerability]]
 
[[Category:Access Control Vulnerability]]
−
 
 
[[Category:Unsafe Mobile Code]]
 
[[Category:Unsafe Mobile Code]]
−
 
 
[[Category:Java]]
 
[[Category:Java]]
−
 
 
[[Category:Implementation]]
 
[[Category:Implementation]]
−
 
 
[[Category:Code Snippet]]
 
[[Category:Code Snippet]]

Revision as of 13:52, 3 October 2008

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

Last revision (mm/dd/yy): 10/3/2008

Vulnerabilities Table of Contents

ASDR Table of Contents


Description

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


Examples

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


References

TBD

Retrieved from "https://wiki.owasp.org/index.php?title=Unsafe_Mobile_Code:_Public_finalize()_Method&oldid=41894"