CWE-577 Variant Draft

EJB Bad Practices: Use of Sockets

This vulnerability occurs when an Enterprise JavaBeans (EJB) component breaks the EJB specification by directly creating or using network sockets.

Definition

What is CWE-577?

This vulnerability occurs when an Enterprise JavaBeans (EJB) component breaks the EJB specification by directly creating or using network sockets.
The EJB specification sets clear rules to ensure components are portable and behave consistently across different application servers. One of these rules explicitly forbids EJB beans from acting as network servers—meaning they must not open sockets to listen for or accept incoming connections. This restriction preserves the server's ability to manage resources, control the bean's lifecycle, and maintain transactional integrity. Allowing an EJB to become a socket server conflicts with its primary role as a managed component serving EJB clients. It can destabilize the container, interfere with clustering and load balancing, and create unpredictable security and performance issues. Instead, socket-based server functionality should be implemented outside the EJB container, in a managed service or a dedicated layer, keeping the bean's design aligned with its intended client-serving architecture.
Real-world impact

Real-world CVEs caused by CWE-577

No public CVE references are linked to this CWE in MITRE's catalog yet.

How attackers exploit it

Step-by-step attacker path

  1. 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.

  2. 2

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

  3. 3

    The previous two examples within any type of Enterprise JavaBean violate the EJB specification by attempting to listen on a socket, accepting connections on a socket, or using a socket for multicast.

Vulnerable code example

Vulnerable Java

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.

Vulnerable Java 
@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() {...}
  }
Secure code example

Secure pseudo

Secure pseudo 
// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
  const safe = validateAndEscape(input);
  return executeWithGuards(safe);
}
What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Prevention checklist

How to prevent CWE-577

  • Architecture and Design / Implementation Do not use Sockets when writing EJBs.
Detection signals

How to detect CWE-577

SAST High

Run static analysis (SAST) on the codebase looking for the unsafe pattern in the data flow.

DAST Moderate

Run dynamic application security testing against the live endpoint.

Runtime Moderate

Watch runtime logs for unusual exception traces, malformed input, or authorization bypass attempts.

Code review Moderate

Code review: flag any new code that handles input from this surface without using the validated framework helpers.

Plexicus auto-fix

Plexicus auto-detects CWE-577 and opens a fix PR in under 60 seconds.

Codex Remedium scans every commit, identifies this exact weakness, and ships a reviewer-ready pull request with the patch. No tickets. No hand-offs.

Get a demo Try Plexicus free
Frequently asked questions

Frequently asked questions

What is CWE-577?

This vulnerability occurs when an Enterprise JavaBeans (EJB) component breaks the EJB specification by directly creating or using network sockets.

How serious is CWE-577?

MITRE has not published a likelihood-of-exploit rating for this weakness. Treat it as medium-impact until your threat model proves otherwise.

What languages or platforms are affected by CWE-577?

MITRE lists the following affected platforms: Java.

How can I prevent CWE-577?

Do not use Sockets when writing EJBs.

How does Plexicus detect and fix CWE-577?

Plexicus's SAST engine matches the data-flow signature for CWE-577 on every commit. When a match is found, our Codex Remedium agent opens a fix PR with the corrected code, tests, and a one-line summary for the reviewer.

Where can I learn more about CWE-577?

MITRE publishes the canonical definition at https://cwe.mitre.org/data/definitions/577.html. You can also reference OWASP and NIST documentation for adjacent guidance.

Related weaknesses

Weaknesses related to CWE-577

CWE-573 Parent

Improper Following of Specification by Caller

This weakness occurs when software fails to properly follow the documented rules, protocols, or requirements of an external component it…

CWE-103 Sibling

Struts: Incomplete validate() Method Definition

This vulnerability occurs in a Struts application when a validator form either completely omits a validate() method or includes one but…

CWE-104 Sibling

Struts: Form Bean Does Not Extend Validation Class

This vulnerability occurs in Apache Struts applications when a form bean class does not properly extend the framework's validation class.…

CWE-243 Sibling

Creation of chroot Jail Without Changing Working Directory

This vulnerability occurs when a program creates a chroot jail but fails to change its current working directory afterward. Because the…

CWE-253 Sibling

Incorrect Check of Function Return Value

This vulnerability occurs when a program misinterprets or improperly validates the return value from a function, causing it to miss…

CWE-296 Sibling

Improper Following of a Certificate's Chain of Trust

This vulnerability occurs when software fails to properly validate the entire certificate chain back to a trusted root authority. This…

CWE-304 Sibling

Missing Critical Step in Authentication

This vulnerability occurs when a software authentication process omits a required step, weakening its overall security.

CWE-325 Sibling

Missing Cryptographic Step

This vulnerability occurs when a software implementation skips a critical step in a cryptographic process, resulting in security that is…

CWE-329 Sibling

Generation of Predictable IV with CBC Mode

This vulnerability occurs when software uses a predictable or reused Initialization Vector (IV) with Cipher Block Chaining (CBC) mode…

Resources

Further reading

Ready when you are

Don't Let Security
Weigh You Down.

Stop choosing between AI velocity and security debt. Plexicus is the only platform that runs Vibe Coding Security and ASPM in parallel — one workflow, every codebase.

Get started free Book a demo