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"
Line 2: | Line 2: | ||
{{Template:Fortify}} | {{Template:Fortify}} | ||
− | [[ | + | __TOC__ |
+ | |||
+ | [[ASDR Table of Contents]] | ||
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}''' | Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}''' | ||
− | |||
− | |||
− | |||
− | |||
+ | [[Category:FIXME|This is the text from the old template. This needs to be rewritten using the new template.]] | ||
==Description== | ==Description== | ||
Line 100: | Line 99: | ||
[[Category:Implementation]] | [[Category:Implementation]] | ||
[[Category:API Abuse]] | [[Category:API Abuse]] | ||
+ | [[Category:Vulnerability]] |
Revision as of 13:07, 30 October 2008
This is a Vulnerability. To view all vulnerabilities, please see the Vulnerability Category page.
Last revision (mm/dd/yy): 10/30/2008
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.