CWE-594: J2EE Framework: Saving Unserializable Objects to Skip to content

Security weakness

CWE-594 J2EE Framework: Saving Unserializable Objects to Disk

A variant-level weakness that can lead to data, pages or code changed and downtime and lost sales. Here is what it is, what it can cost you and how to close it.

  • Senior security engineers
  • 540+ projects delivered
  • Reply within one business day

Quick answer

What is CWE-594?

J2EE Framework: Saving Unserializable Objects to Disk: The J2EE container attempts to write unserializable objects to disk.

Business impact

What CWE-594 could cost your business

MITRE documents what this weakness can do. Here is what that means for a website, store or app.

Integrity

Data, pages or code changed

Prices, orders, content or the code your site runs can be altered without your approval.

  • Modify Application Data

Availability

Downtime and lost sales

Crashes, slowdowns or exhausted resources can take your site, store or app offline.

  • DoS: Crash, Exit, or Restart

Free security check

Is CWE-594 hiding in your site?

A senior engineer checks your site, store or app for this weakness and the rest of the CWE Top 25, then sends a prioritized fix plan within one business day. No obligation.

Official definition

How MITRE defines CWE-594

J2EE Framework: Saving Unserializable Objects to Disk

The J2EE container attempts to write unserializable objects to disk.

In heavy load conditions, most J2EE application frameworks flush objects to disk to manage memory requirements of incoming requests. For example, session scoped objects, and even application scoped objects, are written to disk when required. While these application frameworks do the real work of writing objects to disk, they do not enforce that those objects be serializable, thus leaving the web application vulnerable to crashes induced by serialization failure. An attacker may be able to mount a denial of service attack by sending enough requests to the server to force the web application to save objects to disk.

Weakness ID
CWE-594
Type
Variant
Status
Incomplete
Applies to
Java, Web Based, Web Server
Introduced during
Implementation

Prevention

How to fix CWE-594, phase by phase

Every mitigation from the CWE entry, in the order a project runs: plan, build, test, operate.

  1. 01

    Architecture and Design

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

How we fix it

From finding to fixed: how Codefreex closes CWE-594

  1. Scan and confirm

    We test your site, store or app for this weakness and the rest of the CWE Top 25 with automated scanning and manual review, and confirm what is actually exploitable.

  2. Fix at the source

    We change the code, configuration or dependency that causes it, not just the symptom, and plan the changes to avoid downtime.

  3. Verify the fix

    We retest every finding, check that nothing else broke and hand you a short report you can share with your team, client or auditor.

  4. Keep it fixed

    Updates, monitoring and maintenance so the weakness does not return with the next plugin, theme, app or code change.

FAQ

CWE-594: FAQs

Short answers for owners and developers. Not sure whether your site is affected? Ask us to check.

What is CWE-594?

CWE-594, “J2EE Framework: Saving Unserializable Objects to Disk”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. The J2EE container attempts to write unserializable objects to disk.

How serious is CWE-594?

It can affect integrity, availability, with impacts such as modify application data, dos: crash, exit, or restart. The real risk depends on where the weakness sits and what data or functions it exposes.

How do you 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.

Can Codefreex check my site for CWE-594?

Yes. A senior engineer reviews your site, store or app for CWE-594 and the rest of the CWE Top 25, confirms what is exploitable and sends a prioritized fix plan within one business day. Start with the free security check form on this page.

Which technologies does CWE-594 affect?

MITRE lists it as applicable to Java, Web Based, Web Server. In practice any software that matches the weakness description can be affected, including custom code, plugins, themes and third-party libraries.

Free security check

Find out if CWE-594 affects your site

Send your URL. A senior engineer checks for this weakness and the rest of the CWE Top 25, and replies within one business day with what to fix first.

  • A senior strategist reviews your request, not a sales bot
  • Clear scope, timeline and estimate within one business day
  • Free 30-minute discovery call, no obligation
  • NDA available on request

Weakness data from the Common Weakness Enumeration (CWE®) version 5.0, Copyright © 2006–2026, The MITRE Corporation. CWE is free to use by any organization or individual for any research, development, and/or commercial purposes under the CWE Terms of Use. CWE is a registered trademark of The MITRE Corporation. The business impact, risk profile and plain-English guidance on this page are written by Codefreex and are general information, not a security assessment of your system.