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

From OWASP
Jump to: navigation, search
(Reverting to last version not containing links to www.textnobasace.com)
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Template:Vulnerability}}
+
{{template:CandidateForDeletion}}
{{Template:Fortify}}
 
  
[[Category:FIXME|This is the text from the old template. This needs to be rewritten using the new template.]]
+
#REDIRECT [[Unsafe Mobile Code]]
  
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
 
  
[[ASDR_TOC_Vulnerabilities|Vulnerabilities Table of Contents]]
 
  
[[ASDR Table of Contents]]
+
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
__TOC__
 
  
  
Line 64: Line 60:
  
 
TBD
 
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__
 
__NOTOC__
 
 
[[Category:OWASP ASDR Project]]
 
[[Category:Code Quality Vulnerability]]
 
[[Category:Access Control Vulnerability]]
 
[[Category:Unsafe Mobile Code]]
 
[[Category:Java]]
 
[[Category:Implementation]]
 
[[Category:Code Snippet]]
 

Latest revision as of 18:28, 27 May 2009

Template:CandidateForDeletion

#REDIRECT Unsafe Mobile Code


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


Description

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

TBD

Examples

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


References

TBD