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 Sockets"
Weilin Zhong (talk | contribs) (Added communication category.) |
Weilin Zhong (talk | contribs) |
||
| Line 18: | Line 18: | ||
"The EJB architecture allows an enterprise bean instance to be a network socket client, but it does not allow it to be a network server. Allowing the instance to become a network server would conflict with the basic function of the enterprise bean – to serve the EJB clients." | "The EJB architecture allows an enterprise bean instance to be a network socket client, but it does not allow it to be a network server. Allowing the instance to become a network server would conflict with the basic function of the enterprise bean – to serve the EJB clients." | ||
| + | |||
| + | ==Examples == | ||
| + | |||
| + | ==Related Threats== | ||
| + | |||
| + | ==Related Attacks== | ||
| + | |||
| + | [[:Category:API Abuse Attack]] | ||
| + | |||
| + | ==Related Vulnerabilities== | ||
| + | |||
| + | ==Related Countermeasures== | ||
==References == | ==References == | ||
| Line 23: | Line 35: | ||
[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:API | + | ==Categories== |
| + | |||
| + | [[Category:Use of Dangerous API]] | ||
[[Category:Java]] | [[Category:Java]] | ||
Revision as of 17:56, 18 July 2006
- This article includes content generously donated to OWASP by
This is a Vulnerability. To view all vulnerabilities, please see the Vulnerability Category page.
Abstract
The program violates the Enterprise JavaBeans specification by using sockets.
Description
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 attempt to listen on a socket, accept connections on a socket, or use a socket for multicast."
A requirement that the specification justifies in the following way:
"The EJB architecture allows an enterprise bean instance to be a network socket client, but it does not allow it to be a network server. Allowing the instance to become a network server would conflict with the basic function of the enterprise bean – to serve the EJB clients."
Examples
Related Threats
Related Attacks
Related Vulnerabilities
Related Countermeasures
References
[1] Enterprise JavaBeans 2.1 Specification. Sun Microsystems. http://java.sun.com/products/ejb/docs.html.
