CWE-594 Variant Incomplete

J2EE Framework: Saving Unserializable Objects to Disk

This vulnerability occurs when a J2EE application framework attempts to save objects to disk that cannot be properly serialized, risking application failure.

Definition

What is CWE-594?

This vulnerability occurs when a J2EE application framework attempts to save objects to disk that cannot be properly serialized, risking application failure.
To handle high traffic, J2EE frameworks often move objects from memory to disk. This includes session and application data. However, these frameworks don't always verify that the objects are serializable first. When the system tries to write an unserializable object, the serialization process fails, which can crash the application or cause unpredictable behavior. An attacker can exploit this weakness to cause a denial of service. By flooding the server with requests, they can trigger the framework's disk-writing mechanism. If enough unserializable objects are forced to disk, the repeated serialization failures can overwhelm the application, making it unavailable to legitimate users.
Real-world impact

Real-world CVEs caused by CWE-594

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 Java example, a Customer Entity JavaBean provides access to customer information in a database for a business application. The Customer Entity JavaBean is used as a session scoped object to return customer information to a Session EJB.

Vulnerable Java 
@Entity
  public class Customer {
  		private String id;
  		private String firstName;
  		private String lastName;
  		private Address address;
  		public Customer() {
  		}
  		public Customer(String id, String firstName, String lastName) {...}
  		@Id
  		public String getCustomerId() {...}
  		public void setCustomerId(String id) {...}
  		public String getFirstName() {...}
  		public void setFirstName(String firstName) {...}
  		public String getLastName() {...}
  		public void setLastName(String lastName) {...}
  		@OneToOne()
  		public Address getAddress() {...}
  		public void setAddress(Address address) {...}
  }
Secure code example

Secure Java

However, the Customer Entity JavaBean is an unserialized object which can cause serialization failure and crash the application when the J2EE container attempts to write the object to the system. Session scoped objects must implement the Serializable interface to ensure that the objects serialize properly.

Secure Java 
public class Customer implements Serializable {...}
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-594

  • Architecture and Design / Implementation All objects that become part of session and application scope must implement the java.io.Serializable interface to ensure serializability of containing objects.
Detection signals

How to detect CWE-594

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

This vulnerability occurs when a J2EE application framework attempts to save objects to disk that cannot be properly serialized, risking application failure.

How serious is CWE-594?

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

MITRE lists the following affected platforms: Java.

How can I prevent CWE-594?

All objects that become part of session and application scope must implement the java.io.Serializable interface to ensure serializability of containing objects.

How does Plexicus detect and fix CWE-594?

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

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

Related weaknesses

Weaknesses related to CWE-594

CWE-1076 Parent

Insufficient Adherence to Expected Conventions

This weakness occurs when software code, design, documentation, or other components fail to follow established industry or…

CWE-1045 Sibling

Parent Class with a Virtual Destructor and a Child Class without a Virtual Destructor

This occurs when a base class defines a virtual destructor, but a derived class inherits from it without declaring its own virtual…

CWE-1070 Sibling

Serializable Data Element Containing non-Serializable Item Elements

This weakness occurs when a class or data structure is marked as serializable, but it contains one or more member elements that cannot be…

CWE-1078 Sibling

Inappropriate Source Code Style or Formatting

This weakness occurs when source code violates established style guidelines for formatting, indentation, whitespace, or commenting, making…

CWE-1079 Sibling

Parent Class without Virtual Destructor Method

This occurs when a base class, designed to be inherited from, does not declare its destructor as virtual. This oversight prevents proper…

CWE-1082 Sibling

Class Instance Self Destruction Control Element

This vulnerability occurs when an object's code contains logic that triggers its own deletion or destruction during runtime.

CWE-1087 Sibling

Class with Virtual Method without a Virtual Destructor

This occurs when a class defines a virtual method but does not also provide a virtual destructor.

CWE-1091 Sibling

Use of Object without Invoking Destructor Method

This weakness occurs when a program accesses an object but fails to properly call its destructor or finalizer method. This leaves the…

CWE-1097 Sibling

Persistent Storable Data Element without Associated Comparison Control Element

This weakness occurs when a persistent data object lacks the necessary methods to be properly compared, which can lead to inconsistent or…

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