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"
Weilin Zhong (talk | contribs) (Contents provided by Fortify.) |
Weilin Zhong (talk | contribs) (Moved the definition of mobile code and its security concern to :Category:Unsafe Mobile Code.) |
||
| Line 9: | Line 9: | ||
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. | 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]]. | ||
==Examples == | ==Examples == | ||
| Line 22: | Line 24: | ||
} | } | ||
</pre> | </pre> | ||
| − | |||
| − | |||
==Related Principles== | ==Related Principles== | ||
| Line 42: | Line 42: | ||
[[Category:Access Control Vulnerability]] | [[Category:Access Control Vulnerability]] | ||
| + | |||
| + | [[Category:Unsafe Mobile Code]] | ||
[[Category:Java]] | [[Category:Java]] | ||
Revision as of 17:21, 21 July 2006
This is a Vulnerability. To view all vulnerabilities, please see the Vulnerability Category page.
- This article includes content generously donated to OWASP by
Abstract
The program violates secure coding principles for mobile code by making use of an inner class.
Description
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.
Examples
The following Java Applet code mistakenly makes use of an inner class.
public final class urlTool extends Applet {
private final class urlHelper {
...
}
...
}
