1306
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. In this case, the product 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." The specification justifies this requirement 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."
Relationships
The table(s) below shows the weaknesses and high level categories that are related to this
weakness. These relationships are defined as ChildOf, ParentOf, MemberOr and give insight to
similar items that may exist at higher and lower levels of abstraction. In addition, relationships such
as PeerOf and CanAlsoBe are defined to show similar weaknesses that may want to be explored.
Relevant to the view "Research Concepts" (CWE-1000)
Nature Type ID Name Page
ChildOf 573 Improper Following of Specification by Caller 1298
Applicable Platforms
Language : Java (Prevalence = Undetermined)
Common Consequences
Scope Impact Likelihood
Other Quality Degradation
Potential Mitigations
Phase: Architecture and Design
Phase: Implementation
Do not use Sockets when writing EJBs.
Demonstrative Examples
Example 1:
The following Java example is a simple stateless Enterprise JavaBean that retrieves stock
symbols and stock values. The Enterprise JavaBean creates a socket and listens for and accepts
connections from clients on the socket.
Example Language: Java (Bad)
@Stateless
public class StockSymbolBean implements StockSymbolRemote {
ServerSocket serverSocket = null;
Socket clientSocket = null;
public StockSymbolBean() {
try {
serverSocket = new ServerSocket(Constants.SOCKET_PORT);
} catch (IOException ex) {...}
try {
clientSocket = serverSocket.accept();
} catch (IOException e) {...}
}
public String getStockSymbol(String name) {...}
public BigDecimal getStockValue(String symbol) {...}
private void processClientInputFromSocket() {...}
}
And the following Java example is similar to the previous example but demonstrates the use of
multicast socket connections within an Enterprise JavaBean.
CWE Version 4.14
CWE-578: EJB Bad Practices: Use of Class Loader
CWE-578: EJB Bad Practices: Use of Class Loader