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"

From OWASP
Jump to: navigation, search
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Template:Fortify}}
+
{{template:CandidateForDeletion}}
  
{{Template:Vulnerability}}
+
#REDIRECT [[Failure to follow guideline/specification]]
  
==Abstract==
 
  
The program violates the Enterprise JavaBeans specification by using the class loader.
+
 
 +
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
  
 
==Description==
 
==Description==
 +
 +
The program violates the Enterprise JavaBeans specification by using the class loader.
  
 
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]
 
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]
Line 19: Line 21:
 
"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."
 
"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 ==
+
==Risk Factors==
 +
 
 +
TBD
 +
 
 +
==Examples==
 +
 
 +
TBD
 +
 
 +
==Related [[Attacks]]==
 +
 
 +
* [[Attack 1]]
 +
* [[Attack 2]]
 +
 
  
==Related Threats==
+
==Related [[Vulnerabilities]]==
  
==Related Attacks==
+
* [[Vulnerability 1]]
 +
* [[Vulnerabiltiy 2]]
  
[[:Category:API Abuse Attack]]
 
  
==Related Vulnerabilities==
+
==Related [[Controls]]==
  
==Related Countermeasures==
+
* [[Control 1]]
 +
* [[Control 2]]
  
== References ==
 
  
[1] Enterprise JavaBeans 2.1 Specification. Sun Microsystems. http://java.sun.com/products/ejb/docs.html.
+
==Related [[Technical Impacts]]==
  
==Categories==
+
* [[Technical Impact 1]]
 +
* [[Technical Impact 2]]
  
[[Category:Java]]
 
  
[[Category:Implementation]]
+
==References==
  
[[Category:Use of Dangerous API]]
+
* [1] Enterprise JavaBeans 2.1 Specification. Sun Microsystems. http://java.sun.com/products/ejb/docs.html.

Latest revision as of 23:23, 7 April 2009

Template:CandidateForDeletion

#REDIRECT Failure to follow guideline/specification


Last revision (mm/dd/yy): 04/7/2009

Description

The program violates the Enterprise JavaBeans specification by using the class loader.

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."

Risk Factors

TBD

Examples

TBD

Related Attacks


Related Vulnerabilities


Related Controls


Related Technical Impacts


References