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 Array Declaration"
| Line 3: | Line 3: | ||
#REDIRECT [[Unsafe Mobile Code]] | #REDIRECT [[Unsafe Mobile Code]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
Latest revision as of 23:34, 7 April 2009
#REDIRECT Unsafe Mobile Code
Last revision (mm/dd/yy): 04/7/2009
Description
The program violates secure coding principles for mobile code by declaring an array public, final and static.
In most cases an array declared public, final and static is a bug. Because arrays are mutable objects, the final constraint requires that the array object itself be assigned only once, but makes no guarantees about the values of the array elements. Since the array is public, a malicious program can change the values stored in the array. In most situations the array should be made private.
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 an array public, final and static.
public final class urlTool extends Applet {
public final static URL[] urls;
...
}
Related Attacks
Related Vulnerabilities
Related Controls
Related Technical Impacts
References
TBD
