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
Weilin Zhong (talk | contribs) |
(Reverting to last version not containing links to www.textchigetd.com) |
||
(6 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
− | {{ | + | {{template:CandidateForDeletion}} |
− | {{ | + | |
+ | #REDIRECT [[Failure to follow guideline/specification]] | ||
+ | |||
+ | |||
+ | Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}''' | ||
− | |||
− | |||
==Description== | ==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]. | 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]. | ||
Line 12: | Line 16: | ||
In this case, the program violates the following EJB guideline: | 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." | + | "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: | 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." | + | "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]]== | ||
+ | |||
+ | * [[Attack 1]] | ||
+ | * [[Attack 2]] | ||
− | |||
− | ==Related | + | ==Related [[Vulnerabilities]]== |
− | + | * [[Vulnerability 1]] | |
+ | * [[Vulnerabiltiy 2]] | ||
− | |||
− | ==Related | + | ==Related [[Controls]]== |
− | + | * [[Control 1]] | |
+ | * [[Control 2]] | ||
− | |||
− | == | + | ==Related [[Technical Impacts]]== |
− | [[ | + | * [[Technical Impact 1]] |
+ | * [[Technical Impact 2]] | ||
− | |||
− | + | ==References== | |
− | [ | + | * [1] Enterprise JavaBeans 2.1 Specification. Sun Microsystems. http://java.sun.com/products/ejb/docs.html. |
Latest revision as of 18:27, 27 May 2009
#REDIRECT Failure to follow guideline/specification
Last revision (mm/dd/yy): 05/27/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.