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"
From OWASP
Deleted user (talk | contribs) |
(Reverting to last version not containing links to s1.shard.jp) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
{{template:CandidateForDeletion}} | {{template:CandidateForDeletion}} | ||
| Line 56: | Line 23: | ||
"The EJB architecture allows an enterprise bean instance to be a network socket client, but it does not allow it to be | "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 | a network server. Allowing the instance to become a network server would conflict with the basic function of the | ||
| − | enterprise bean | + | enterprise bean – to serve the EJB clients." |
==Risk Factors== | ==Risk Factors== | ||
Latest revision as of 12:50, 3 June 2009
#REDIRECT Failure to follow guideline/specification
Last revision (mm/dd/yy): 06/3/2009
Description
The program violates the Enterprise JavaBeans specification by listening on a socket or accept connections on a socket. However it can act as a network socket client.
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."
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.
