CWE-577: EJB Bad Practices: Use of Sockets

Extended 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. 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."

Code Examples & CVEs

Demonstrative Examples

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.

And the following Java example is similar to the previous example but demonstrates the use of multicast socket connections within an Enterprise JavaBean.

BadJava

@Statelesspublic 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.

BadJava

@Statelesspublic class StockSymbolBean extends Thread implements StockSymbolRemote {                                                     ServerSocket serverSocket = null;Socket clientSocket = null;boolean listening = false;                            public StockSymbolBean() {                               try {serverSocket = new ServerSocket(Constants.SOCKET_PORT);} catch (IOException ex) {...}                                  listening = true;while(listening) {start();}                            }                            public String getStockSymbol(String name) {...}                            public BigDecimal getStockValue(String symbol) {...}                            public void run() {try {clientSocket = serverSocket.accept();} catch (IOException e) {...}...}                                               }

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-577 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-577, EJB Bad Practices: Use of Sockets, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Address EJB Bad Practices: Use of Sockets during Architecture and Design

MITRE associates mitigation with Architecture and Design, and Implementation; recorded impacts include Quality Degradation; related weaknesses include CWE-573. Use these source-defined anchors to turn CWE-577 into implementation, review, and verification checks for the affected component.

CWE-577: EJB Bad Practices: Use of Sockets — MITRE CWE

Triage CWE-577 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-577, EJB Bad Practices: Use of Sockets, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-577

Apply MITRE's full root-cause mapping guidance when using CWE-577, EJB Bad Practices: Use of Sockets. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping Guidance — MITRE CWE

Validate CWE-577 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-577, EJB Bad Practices: Use of Sockets. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick Tips — MITRE CWE

Frequently Asked Questions

What is CWE-577: EJB Bad Practices: Use of Sockets?+

CWE-577: EJB Bad Practices: Use of Sockets is a Common Weakness Enumeration (CWE) entry maintained by MITRE. 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."

What are the security consequences of EJB Bad Practices: Use of Sockets?+

If exploited, CWE-577 (EJB Bad Practices: Use of Sockets) it can compromise Other, leading to outcomes such as Quality Degradation.

How do you prevent or mitigate EJB Bad Practices: Use of Sockets?+

Recommended mitigations for CWE-577 include: Do not use Sockets when writing EJBs.

Which programming languages are affected by EJB Bad Practices: Use of Sockets?+

CWE-577 commonly affects Java. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-577 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

CWE-577: EJB Bad Practices: Use of Sockets

Extended Description

Technical Details

Applicable To

Security Consequences

Scope

Impact

Mitigation Strategies

Phase

Description

Detection Methods