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 AWT/Swing"
From OWASP
Weilin Zhong (talk | contribs) |
|||
| (4 intermediate revisions by 2 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 AWT/Swing. | ||
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 18: | Line 20: | ||
"Most servers do not allow direct interaction between an application program and a keyboard/display attached to the server system." | "Most servers do not allow direct interaction between an application program and a keyboard/display attached to the server system." | ||
| − | |||
| − | ==Related | + | ==Risk Factors== |
| + | |||
| + | TBD | ||
| + | |||
| + | |||
| + | ==Examples== | ||
| + | |||
| + | TBD | ||
| + | |||
| + | ==Related [[Attacks]]== | ||
| + | |||
| + | * [[Attack 1]] | ||
| + | * [[Attack 2]] | ||
| − | |||
| − | ==Related Vulnerabilities== | + | ==Related [[Vulnerabilities]]== |
| − | + | * [[Vulnerability 1]] | |
| + | * [[Vulnerabiltiy 2]] | ||
| − | == | + | ==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 23:23, 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 AWT/Swing.
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:
"An enterprise bean must not use the AWT functionality to attempt to output information to a display, or to input information from a keyboard."
A requirement that the specification justifies in the following way:
"Most servers do not allow direct interaction between an application program and a keyboard/display attached to the server system."
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.
