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 java.io"
From OWASP
Line 3: | Line 3: | ||
#REDIRECT [[Failure to follow guideline/specification]] | #REDIRECT [[Failure to follow guideline/specification]] | ||
− | |||
− | |||
− | |||
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}''' | Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}''' |
Revision as of 23:24, 7 April 2009
#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 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
- [1] Enterprise JavaBeans 2.1 Specification. Sun Microsystems. http://java.sun.com/products/ejb/docs.html.