CWE-579 Variante Brouillon

J2EE Bad Practices: Non-serializable Object Stored in Session

This vulnerability occurs when a Java application stores an object in the user's session that cannot be serialized, which can break critical application features and hurt reliability.

Définition

What is CWE-579?

This vulnerability occurs when a Java application stores an object in the user's session that cannot be serialized, which can break critical application features and hurt reliability.

Modern Java applications often run across multiple servers (JVMs) for better performance and uptime. To present a seamless experience, the application server needs to copy a user's session data between these servers, especially if one fails. This replication process requires every object stored in the `HttpSession` to be serializable—that is, convertible into a byte stream for transfer. If a non-serializable object is placed in the session, this failover mechanism breaks, potentially causing errors during server scaling or outages. For developers, this means any class whose instance is added to the session via `setAttribute()` must implement the `java.io.Serializable` interface. Common culprits include custom helper classes, third-party library objects, or database connections that weren't designed for serialization. Failing to ensure this prevents session replication, undermining the reliability benefits of a clustered deployment and leading to inconsistent user experiences during infrastructure changes.

Impact réel

Real-world CVEs caused by CWE-579

Aucune référence CVE publique n'est liée à ce CWE dans le catalogue MITRE pour le moment.

Comment les attaquants l'exploitent

Parcours de l'attaquant étape par étape

1
Identifier un chemin de code qui traite des entrées non fiables sans validation.
2
Élaborer une charge utile qui exploite le comportement non sécurisé — injection, traversal, débordement ou abus de logique.
3
Délivrer la charge utile via une requête normale et observer la réaction de l'application.
4
Itérer jusqu'à ce que la réponse divulgue des données, exécute le code de l'attaquant ou élève les privilèges.

Exemple de code vulnérable

Vulnerable Java

The following class adds itself to the session, but because it is not serializable, the session can no longer be replicated.

Vulnérable Java

public class DataGlob {
  		String globName;
  		String globValue;
  		public void addToSession(HttpSession session) {
  			session.setAttribute("glob", this);
  		}
  }

Exemple de code sécurisé

Secure pseudo

Sécurisé 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.

Liste de contrôle de prévention

How to prevent CWE-579

Implementation In order for session replication to work, the values the product stores as attributes in the session must implement the Serializable interface.

Signaux de détection

How to detect CWE-579

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

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

Questions fréquentes

Frequently asked questions

Qu'est-ce que CWE-579 ?

This vulnerability occurs when a Java application stores an object in the user's session that cannot be serialized, which can break critical application features and hurt reliability.

Quelle est la gravité de CWE-579 ?

MITRE n'a pas publié de note de probabilité d'exploitation pour cette faiblesse. Traitez-la comme un impact moyen jusqu'à ce que votre modèle de menace prouve le contraire.

Quels langages ou plateformes sont affectés par CWE-579 ?

MITRE lists the following affected platforms: Java.

Comment puis-je prévenir CWE-579 ?

In order for session replication to work, the values the product stores as attributes in the session must implement the Serializable interface.

Comment Plexicus détecte et corrige CWE-579 ?

Le moteur SAST de Plexicus reconnaît la signature de flux de données de CWE-579 à chaque commit. Lorsqu'une correspondance est trouvée, notre agent Codex Remedium ouvre une PR de correction avec le code corrigé, les tests et un résumé d'une ligne pour le relecteur.

Où puis-je en savoir plus sur CWE-579 ?

MITRE publie la définition canonique à https://cwe.mitre.org/data/definitions/579.html. Vous pouvez également consulter la documentation OWASP et NIST pour des conseils adjacents.

Faiblesses associées

Weaknesses related to CWE-579

CWE-573 Parent

Prêt à valider ce qui compte.

Plexicus est Proof-Driven AppSec : findings validés, compréhension contextuelle et remédiation relue — ancrée dans la preuve, scopée avec vous.

Réserver un Pentest

J2EE Bad Practices: Non-serializable Object Stored in Session

What is CWE-579?

Real-world CVEs caused by CWE-579

Parcours de l'attaquant étape par étape

Vulnerable Java

Secure pseudo

How to prevent CWE-579

How to detect CWE-579

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

Frequently asked questions

Weaknesses related to CWE-579

Improper Following of Specification by Caller

Struts: Incomplete validate() Method Definition

Struts: Form Bean Does Not Extend Validation Class

Creation of chroot Jail Without Changing Working Directory

Incorrect Check of Function Return Value

Improper Following of a Certificate's Chain of Trust

Missing Critical Step in Authentication

Missing Cryptographic Step

Generation of Predictable IV with CBC Mode

Further reading

Prêt à valider ce qui compte.

Vérifiez si l'AI Swarm Pentest convient à votre environnement.

Demande reçue. Réservez la prochaine étape.

Sample evidence handover

Server-Side Request Forgery in `webhooks/receiver`