Difference between revisions of "Unsafe Mobile Code"

From OWASP
Jump to: navigation, search
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 returning a private array variable from a public access method.
 
  
 
==Description==
 
==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.
 
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.
Line 12: Line 20:
 
For more details about what is mobile code and its security concerns, please see [[:Category:Unsafe Mobile Code]].
 
For more details about what is 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 returns a private array variable from a public access method.
 
The following Java Applet code mistakenly returns a private array variable from a public access method.
Line 26: Line 42:
 
</pre>
 
</pre>
  
==Related Principles==
 
  
[[Use encapsulation]]
+
==Related [[Attacks]]==
  
==Related Threats==
+
* [[Attack 1]]
 +
* [[Attack 2]]
  
==Related Attacks==
 
  
==Related Vulnerabilities==
+
==Related [[Vulnerabilities]]==
  
==Related Countermeasures==
+
* [[Vulnerability 1]]
 +
* [[Vulnerabiltiy 2]]
  
==Categories==
 
  
[[Category:Code Quality Vulnerability]]
 
  
[[Category:Access Control Vulnerability]]
+
==Related [[Controls]]==
  
[[Category:Java]]
+
* [[Use encapsulation]]
  
[[Category:Implementation]]
+
==Related [[Technical Impacts]]==
  
[[Category:Code Snippet]]
+
* [[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:Access Control Vulnerability]]
 +
[[Category:Java]]
 +
[[Category:Implementation]]
 +
[[Category:Code Snippet]]
 
[[Category:Unsafe Mobile Code]]
 
[[Category:Unsafe Mobile Code]]

Revision as of 08:28, 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 Fortify.JPG.

Last revision (mm/dd/yy): 10/3/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