J2EE Bad Practices: Direct Use of Sockets

Description

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

Extended Description

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.

Common Consequences 1

Scope: Other

Impact: Quality Degradation

Detection Methods 1

Automated Static AnalysisHigh

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

Potential Mitigations 1

Phase: Architecture and Design

Use framework method calls instead of using sockets directly.

Demonstrative Examples 1

ID : DX-197

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

Code Example:

Bad

Java

java

// Perform servlet tasks.* ...

java

java

A Socket object is created directly within the Java servlet, which is a dangerous way to manage remote connections.

References 1

Seven Pernicious Kingdoms: A Taxonomy of Software Security Errors

Katrina Tsipenyuk, Brian Chess, and Gary McGraw

NIST Workshop on Software Security Assurance Tools Techniques and Metrics • NIST

07-11-2005

https://samate.nist.gov/SSATTM_Content/papers/Seven%20Pernicious%20Kingdoms%20-%20Taxonomy%20of%20Sw%20Security%20Errors%20-%20Tsipenyuk%20-%20Chess%20-%20McGraw.pdf

ID: REF-6

Applicable Platforms

Languages:

Java : Undetermined

Modes of Introduction

Implementation

Related Weaknesses

ChildOf:

Use of Low-Level Functionality (CWE-695)

Taxonomy Mapping

7 Pernicious Kingdoms
Software Fault Patterns