CWE-245 Variant Draft

J2EE Bad Practices: Direct Management of Connections

This vulnerability occurs when a J2EE application handles database connections directly instead of using the container's built-in connection management system.

Definition

What is CWE-245?

This vulnerability occurs when a J2EE application handles database connections directly instead of using the container's built-in connection management system.
J2EE standards explicitly prohibit applications from managing their own database connections. Instead, developers must use the container's resource management facilities to obtain connections. Every major J2EE container provides robust, pooled connection management as part of its core framework—bypassing this system violates the platform's fundamental architecture. Recreating connection pooling within an application is both complex and prone to critical errors like connection leaks, improper cleanup, and performance bottlenecks. Using the container's proven management layer eliminates these risks while ensuring optimal resource utilization, which is precisely why direct connection management is considered a bad practice and security vulnerability.
Real-world impact

Real-world CVEs caused by CWE-245

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

    Identify a code path that handles untrusted input without validation.

  2. 2

    Craft a payload that exercises the unsafe behavior — injection, traversal, overflow, or logic abuse.

  3. 3

    Deliver the payload through a normal request and observe the application's reaction.

  4. 4

    Iterate until the response leaks data, executes attacker code, or escalates privileges.

Vulnerable code example

Vulnerable Java

In the following example, the class DatabaseConnection opens and manages a connection to a database for a J2EE application. The method openDatabaseConnection opens a connection to the database using a DriverManager to create the Connection object conn to the database specified in the string constant CONNECT_STRING.

Vulnerable Java 
public class DatabaseConnection {
  		private static final String CONNECT_STRING = "jdbc:mysql://localhost:3306/mysqldb";
  		private Connection conn = null;
  		public DatabaseConnection() {
  		}
  		public void openDatabaseConnection() {
  			try {
  				conn = DriverManager.getConnection(CONNECT_STRING);
  			} catch (SQLException ex) {...}
  		}
  		// Member functions for retrieving database connection and accessing database
  		...
  }
Secure code example

Secure Java

The use of the DriverManager class to directly manage the connection to the database violates the J2EE restriction against the direct management of connections. The J2EE application should use the web application container's resource management facilities to obtain a connection to the database as shown in the following example.

Secure Java 
public class DatabaseConnection {
  		private static final String DB_DATASRC_REF = "jdbc:mysql://localhost:3306/mysqldb";
  		private Connection conn = null;
  		public DatabaseConnection() {
  		}
  		public void openDatabaseConnection() {
  				try {
  						InitialContext ctx = new InitialContext();
  						DataSource datasource = (DataSource) ctx.lookup(DB_DATASRC_REF);
  						conn = datasource.getConnection();
  				} catch (NamingException ex) {...}
  				} catch (SQLException ex) {...}
  		}
  		// Member functions for retrieving database connection and accessing database
  		...
  }
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-245

  • Architecture Use safe-by-default frameworks and APIs that prevent the unsafe pattern from being expressible.
  • Implementation Validate input at trust boundaries; use allowlists, not denylists.
  • Implementation Apply the principle of least privilege to credentials, file paths, and runtime permissions.
  • Testing Cover this weakness in CI: SAST rules + targeted unit tests for the data flow.
  • Operation Monitor logs for the runtime signals listed in the next section.
Detection signals

How to detect CWE-245

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

Plexicus auto-fix

Plexicus auto-detects CWE-245 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-245?

This vulnerability occurs when a J2EE application handles database connections directly instead of using the container's built-in connection management system.

How serious is CWE-245?

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

MITRE lists the following affected platforms: Java.

How can I prevent CWE-245?

Use safe-by-default frameworks, validate untrusted input at trust boundaries, and apply the principle of least privilege. Cover the data-flow signature in CI with SAST.

How does Plexicus detect and fix CWE-245?

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

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

Related weaknesses

Weaknesses related to CWE-245

CWE-695 Parent

Use of Low-Level Functionality

This vulnerability occurs when code bypasses high-level framework controls by directly using low-level system functions, violating the…

CWE-111 Sibling

Direct Use of Unsafe JNI

This weakness occurs when a Java application directly calls native code through the Java Native Interface (JNI), exposing the entire…

CWE-246 Sibling

J2EE Bad Practices: Direct Use of Sockets

This vulnerability occurs when a J2EE application creates network sockets directly, bypassing the container-managed communication…

CWE-383 Sibling

J2EE Bad Practices: Direct Use of Threads

Creating or managing threads directly within a J2EE application is a risky practice that violates the platform's standards and often leads…

CWE-574 Sibling

EJB Bad Practices: Use of Synchronization Primitives

This vulnerability occurs when an Enterprise JavaBeans (EJB) component improperly uses thread synchronization primitives, violating the…

CWE-575 Sibling

EJB Bad Practices: Use of AWT Swing

This vulnerability occurs when an Enterprise JavaBeans (EJB) component incorrectly uses AWT or Swing UI toolkits, violating the EJB…

CWE-576 Sibling

EJB Bad Practices: Use of Java I/O

This vulnerability occurs when an Enterprise JavaBeans (EJB) component incorrectly uses Java I/O (java.io) operations to access the file…

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.