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: Inner Class"
| Line 2: | Line 2: | ||
{{Template:Fortify}} | {{Template:Fortify}} | ||
| − | [[Category:FIXME|This is the text from the old template. This needs to be rewritten using the new template | + | [[Category:FIXME|This is the text from the old template. This needs to be rewritten using the new template, needs review]] |
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}''' | Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}''' | ||
| Line 65: | Line 65: | ||
TBD | TBD | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
__NOTOC__ | __NOTOC__ | ||
| Line 96: | Line 72: | ||
[[Category:OWASP ASDR Project]] | [[Category:OWASP ASDR Project]] | ||
[[Category:Code Quality Vulnerability]] | [[Category:Code Quality Vulnerability]] | ||
| − | [[Category: | + | [[Category:Session Management Vulnerability]] |
| + | [[Category: Authorization Vulnerability]] | ||
[[Category:Unsafe Mobile Code]] | [[Category:Unsafe Mobile Code]] | ||
[[Category:Java]] | [[Category:Java]] | ||
[[Category:Implementation]] | [[Category:Implementation]] | ||
[[Category:Code Snippet]] | [[Category:Code Snippet]] | ||
Revision as of 13:18, 13 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
Last revision (mm/dd/yy): 10/13/2008
Vulnerabilities Table of Contents
Description
The program violates secure coding principles for mobile code by making use of an inner class.
Inner classes quietly introduce several security concerns because of the way they are translated into Java bytecode. In Java source code, it appears that an inner class can be declared to be accessible only by the enclosing class, but Java bytecode has no concept of an inner class, so the compiler must transform an inner class declaration into a peer class with package level access to the original outer class. More insidiously, since an inner class can access private fields in their enclosing class, once an inner class becomes a peer class in bytecode, the compiler converts private fields accessed by the inner class into protected fields.
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 makes use of an inner class.
public final class urlTool extends Applet {
private final class urlHelper {
...
}
...
}
Related Attacks
Related Vulnerabilities
Related Controls
Related Technical Impacts
References
TBD
