CWE-246 Variant Draft

J2EE Bad Practices: Direct Use of Sockets

This vulnerability occurs when a J2EE application creates network sockets directly, bypassing the container-managed communication framework provided by the platform.

Definition

What is CWE-246?

This vulnerability occurs when a J2EE application creates network sockets directly, bypassing the container-managed communication framework provided by the platform.

The J2EE specification restricts direct socket use primarily for connecting to legacy systems when no higher-level alternative exists. When developers implement custom network protocols or even re-implement standard ones, they must solve complex security challenges—like proper authentication, encryption, and input validation—that are already handled by the platform's tested frameworks. Without deep security expertise, these custom solutions often introduce critical flaws that attackers can exploit. Managing this at scale is difficult; an ASPM like Plexicus can help you track and remediate these flaws across your entire stack. While SAST tools can flag the direct socket usage pattern, Plexicus uses AI to analyze the context and suggest the specific framework-based code fix, such as replacing raw sockets with a managed service, saving hours of manual investigation and rewrite.

Real-world impact

Real-world CVEs caused by CWE-246

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

How attackers exploit it

Step-by-step attacker path

1
Identify a code path that handles untrusted input without validation.
2
Craft a payload that exercises the unsafe behavior — injection, traversal, overflow, or logic abuse.
3
Deliver the payload through a normal request and observe the application's reaction.
4
Iterate until the response leaks data, executes attacker code, or escalates privileges.

Vulnerable code example

Vulnerable Java

The following example opens a socket to connect to a remote server.

Vulnerable Java

public void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
```
// Perform servlet tasks.* 
  		...
  		
  		
  		 *// Open a socket to a remote server (bad).* 
  		Socket sock = null;
  		
  		try {
  		```
  				sock = new Socket(remoteHostname, 3000);
```
// Do something with the socket.* 
  				...} catch (Exception e) {
  		```
  			...
  		}
  }

Secure code example

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-246

Architecture and Design Use framework method calls instead of using sockets directly.

Detection signals

How to detect CWE-246

Automated Static Analysis High

Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)

CWE-246

Don't catalog this weakness. Prove it's reachable.

Plexicus turns CWE catalogs into evidence: every CWE-pattern is matched against your real code graph, reach is proven on a sandbox clone, and verified findings ship as reviewed PRs.

Request AI Swarm Pentest

Frequently asked questions

What is CWE-246?

This vulnerability occurs when a J2EE application creates network sockets directly, bypassing the container-managed communication framework provided by the platform.

How serious is CWE-246?

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-246?

MITRE lists the following affected platforms: Java.

How can I prevent CWE-246?

Use framework method calls instead of using sockets directly.

How does Plexicus detect and fix CWE-246?

Plexicus's SAST engine matches the data-flow signature for CWE-246 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-246?

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

Related weaknesses

Weaknesses related to CWE-246

CWE-695 Parent

J2EE Bad Practices: Direct Use of Sockets

What is CWE-246?

Real-world CVEs caused by CWE-246

Step-by-step attacker path

Vulnerable Java

Secure pseudo

How to prevent CWE-246

How to detect CWE-246

Don't catalog this weakness. Prove it's reachable.

Frequently asked questions

Weaknesses related to CWE-246

Use of Low-Level Functionality

Direct Use of Unsafe JNI

J2EE Bad Practices: Direct Management of Connections

J2EE Bad Practices: Direct Use of Threads

EJB Bad Practices: Use of Synchronization Primitives

EJB Bad Practices: Use of AWT Swing

EJB Bad Practices: Use of Java I/O

Further reading

Ready to validate what matters?

Check whether AI Swarm Pentest fits your environment.

Request received. Book the next step.

Sample evidence handover

Server-Side Request Forgery in `webhooks/receiver`