Difference between revisions of "Unsafe Mobile Code"

From OWASP
Jump to: navigation, search
Line 69: Line 69:
  
 
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__
Line 100: Line 76:
 
[[Category:OWASP ASDR Project]]
 
[[Category:OWASP ASDR Project]]
 
[[Category:Code Quality Vulnerability]]
 
[[Category:Code Quality Vulnerability]]
[[Category:Access Control Vulnerability]]
+
[[Category:Authentication Vulnerability]]
 
[[Category:Java]]
 
[[Category:Java]]
 
[[Category:Implementation]]
 
[[Category:Implementation]]
 
[[Category:Code Snippet]]
 
[[Category:Code Snippet]]
 
[[Category:Unsafe Mobile Code]]
 
[[Category:Unsafe Mobile Code]]

Revision as of 10:06, 9 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 Fortify.JPG.

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

Vulnerabilities Table of Contents

ASDR Table of Contents

Contents


Description

The program violates secure coding principles for mobile code by returning a private array variable from a public access method.

Returning a private array variable from a public access method allows the calling code to modify the contents of the array, effectively giving the array public access and contradicting the intentions of the programmer who made it private.

For more details about what is 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 returns a private array variable from a public access method.

	public final class urlTool extends Applet {
		private URL[] urls;
		public URL[] getURLs() {
			return urls;
		}
			...
	}


Related Attacks


Related Vulnerabilities


Related Controls

Related Technical Impacts


References

TBD