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: Dangerous Public Field"

Jump to: navigation, search
Line 1: Line 1:
#REDIRECT [[Unsafe Mobile Code]]
Line 8: Line 10:
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
[[Category:FIXME|This is the text from the old template. This needs to be rewritten using the new template.]]
Line 66: Line 66:
[[Category:OWASP ASDR Project]]
[[Category:Code Quality Vulnerability]]
[[Category:Authenticationl Vulnerability]]
[[Category:Unsafe Mobile Code]]
[[Category:Code Snippet]]

Revision as of 16:38, 17 February 2009


#REDIRECT Unsafe Mobile Code

ASDR Table of Contents

Last revision (mm/dd/yy): 02/17/2009


The program violates secure coding principles for mobile code by declaring a member variable public but not final.

All public member variables in an Applet and in classes used by an Applet should be declared final to prevent an attacker from manipulating or gaining unauthorized access to the internal state of the Applet.

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

Risk Factors



The following Java Applet code mistakenly declares a member variable public but not final.

	public final class urlTool extends Applet {
		public URL url;

Related Attacks

Related Vulnerabilities

Related Controls

Related Technical Impacts