VariantDraft

CWE-577EJB Bad Practices: Use of Sockets

Category: other

Description

The product violates the Enterprise JavaBeans (EJB) specification by using sockets. 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."

Common consequences· 1

  • Other — Quality Degradation

Potential mitigations· 1

  • [Architecture and Design, Implementation]Do not use Sockets when writing EJBs.

References

  1. https://cwe.mitre.org/data/definitions/577.html

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.

CWE
EJB Bad Practices: Use of Class Loader
CWE
EJB Bad Practices: Use of Synchronization Primitives
CWE
EJB Bad Practices: Use of AWT Swing
CWE
EJB Bad Practices: Use of Java I/O
CWE
J2EE Bad Practices: Direct Use of Sockets
CWE
J2EE Bad Practices: Non-serializable Object Stored in Session
Sourced from MITRE CWE 4.20. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.