Difference between revisions of "EJB Bad Practices: Use of java.io"

From OWASP
Jump to: navigation, search
Line 1: Line 1:
−
{{Template:Vulnerability}}
+
{{template:CandidateForDeletion}}
−
{{Template:Fortify}}
+
 
 +
#REDIRECT [[Failure to follow guideline/specification]]
  
 
__TOC__
 
__TOC__
Line 9: Line 10:
  
  
−
[[Category:FIXME|This is the text from the old template. This needs to be rewritten using the new template.]]
 
  
 
==Description==
 
==Description==
Line 63: Line 63:
  
 
* [1] Enterprise JavaBeans 2.1 Specification. Sun Microsystems. http://java.sun.com/products/ejb/docs.html.
 
* [1] Enterprise JavaBeans 2.1 Specification. Sun Microsystems. http://java.sun.com/products/ejb/docs.html.
−
 
−
 
−
[[Category:FIXME|add links
 
−
 
−
In addition, one should classify vulnerability based on the following subcategories: Ex:<nowiki>[[Category:Error Handling Vulnerability]]</nowiki>
 
−
 
−
Availability Vulnerability
 
−
 
−
Authorization Vulnerability
 
−
 
−
Authentication Vulnerability
 
−
 
−
Concurrency Vulnerability
 
−
 
−
Configuration Vulnerability
 
−
 
−
Cryptographic Vulnerability
 
−
 
−
Encoding Vulnerability
 
−
 
−
Error Handling Vulnerability
 
−
 
−
Input Validation Vulnerability
 
−
 
−
Logging and Auditing Vulnerability
 
−
 
−
Session Management Vulnerability]]
 
−
 
−
__NOTOC__
 
−
 
−
 
−
[[Category:OWASP ASDR Project]]
 
−
[[Category:Use of Dangerous API]]
 
−
[[Category:Java]]
 
−
[[Category:Implementation]]
 
−
[[Category:API Abuse]]
 
−
[[Category:Vulnerability]]
 

Revision as of 13:53, 17 February 2009

Template:CandidateForDeletion 

#REDIRECT Failure to follow guideline/specification

ASDR Table of Contents

Last revision (mm/dd/yy): 02/17/2009


Description

The program violates the Enterprise JavaBeans specification by using the java.io package.

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 [10].

In this case, the program violates the following EJB guideline: 

 "An enterprise bean must not use the java.io package to attempt to access files and directories in the file system."

A requirement that the specification justifies in the following way: 

 "The file system APIs are not well-suited for business components to access data. Business components should use a 
 resource manager API, such as JDBC, to store data."


Risk Factors

TBD


Examples

TBD

Related Attacks


Related Vulnerabilities


Related Controls


Related Technical Impacts


References

Retrieved from "https://wiki.owasp.org/index.php?title=EJB_Bad_Practices:_Use_of_java.io&oldid=54589"