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 "EJB Bad Practices: Use of Class Loader"
Weilin Zhong (talk | contribs) |
Weilin Zhong (talk | contribs) |
||
| Line 24: | Line 24: | ||
==Related Attacks== | ==Related Attacks== | ||
| − | |||
| − | |||
==Related Vulnerabilities== | ==Related Vulnerabilities== | ||
| Line 42: | Line 40: | ||
[[Category:Use of Dangerous API]] | [[Category:Use of Dangerous API]] | ||
| + | |||
| + | [[Category:API Abuse]] | ||
Revision as of 18:34, 18 July 2006
- This article includes content generously donated to OWASP by
This is a Vulnerability. To view all vulnerabilities, please see the Vulnerability Category page.
Abstract
The program violates the Enterprise JavaBeans specification by using the class loader.
Description
The Enterprise JavaBeans specification requires that every bean provider follow a set of programming guidelines designed to ensure that the bean will be portable and behave consistently in any EJB container. [1]
In this case, the program violates the following EJB guideline:
"The enterprise bean must not attempt to create a class loader; obtain the current class loader; set the context class loader; set security manager; create a new security manager; stop the JVM; or change the input, output, and error streams."
A requirement that the specification justifies in the following way:
"These functions are reserved for the EJB container. Allowing the enterprise bean to use these functions could compromise security and decrease the container's ability to properly manage the runtime environment."
Examples
Related Threats
Related Attacks
Related Vulnerabilities
Related Countermeasures
References
[1] Enterprise JavaBeans 2.1 Specification. Sun Microsystems. http://java.sun.com/products/ejb/docs.html.
