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 Variante Rascunho
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.
Definição
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.
Impacto no mundo real
Real-world CVEs caused by CWE-579
Ainda não há referências CVE públicas associadas a este CWE no catálogo da MITRE.
Como os atacantes a exploram
Trajeto do atacante passo a passo
- 1
Identificar um caminho de código que trata input não confiável sem validação.
- 2
Criar um payload que explora o comportamento inseguro — injeção, traversal, overflow ou abuso de lógica.
- 3
Entregar o payload através de um pedido normal e observar a reação da aplicação.
- 4
Iterar até que a resposta exponha dados, execute código do atacante ou escale privilégios.
Exemplo de código vulnerável
Vulnerable Java
The following class adds itself to the session, but because it is not serializable, the session can no longer be replicated.
public class DataGlob {
String globName;
String globValue;
public void addToSession(HttpSession session) {
session.setAttribute("glob", this);
}
} Exemplo de código seguro
Secure 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.
Lista de verificação de prevenção
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.
Sinais de deteção
How to detect CWE-579
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.
Perguntas frequentes O que é o CWE-579?
Qual a gravidade do CWE-579?
Que linguagens ou plataformas são afetadas pelo CWE-579?
Como posso prevenir o CWE-579?
Como é que o Plexicus deteta e corrige o CWE-579?
Onde posso saber mais sobre o CWE-579?
Frequently asked questions
O que é o 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.
Qual a gravidade do CWE-579?
A MITRE não publicou uma classificação de probabilidade de exploração para esta fraqueza. Trate-a como impacto médio até o seu modelo de ameaças provar o contrário.
Que linguagens ou plataformas são afetadas pelo CWE-579?
MITRE lists the following affected platforms: Java.
Como posso prevenir o CWE-579?
In order for session replication to work, the values the product stores as attributes in the session must implement the Serializable interface.
Como é que o Plexicus deteta e corrige o CWE-579?
O motor SAST do Plexicus correlaciona a assinatura de fluxo de dados do CWE-579 em cada commit. Quando é encontrada uma correspondência, o nosso agente Codex Remedium abre um PR de correção com o código corrigido, testes e um resumo de uma linha para o revisor.
Onde posso saber mais sobre o CWE-579?
A MITRE publica a definição canónica em https://cwe.mitre.org/data/definitions/579.html. Pode também consultar a documentação da OWASP e do NIST para orientações adjacentes.
Fraquezas relacionadas
Weaknesses related to CWE-579
CWE-573 Pai
Improper Following of Specification by Caller
This weakness occurs when software fails to properly follow the documented rules, protocols, or requirements of an external component it…
CWE-103 Irmão
Struts: Incomplete validate() Method Definition
This vulnerability occurs in a Struts application when a validator form either completely omits a validate() method or includes one but…
CWE-104 Irmão
Struts: Form Bean Does Not Extend Validation Class
This vulnerability occurs in Apache Struts applications when a form bean class does not properly extend the framework's validation class.…
CWE-243 Irmão
Creation of chroot Jail Without Changing Working Directory
This vulnerability occurs when a program creates a chroot jail but fails to change its current working directory afterward. Because the…
CWE-253 Irmão
Incorrect Check of Function Return Value
This vulnerability occurs when a program misinterprets or improperly validates the return value from a function, causing it to miss…
CWE-296 Irmão
Improper Following of a Certificate's Chain of Trust
This vulnerability occurs when software fails to properly validate the entire certificate chain back to a trusted root authority. This…
CWE-304 Irmão
Missing Critical Step in Authentication
This vulnerability occurs when a software authentication process omits a required step, weakening its overall security.
CWE-325 Irmão
Missing Cryptographic Step
This vulnerability occurs when a software implementation skips a critical step in a cryptographic process, resulting in security that is…
CWE-329 Irmão
Generation of Predictable IV with CBC Mode
This vulnerability occurs when software uses a predictable or reused Initialization Vector (IV) with Cipher Block Chaining (CBC) mode…
Pronto para validar o que importa?
Pronto para validar o que importa.
O Plexicus é Proof-Driven AppSec: achados validados, compreensão contextual e remediação revisada — ancorada em evidência, escopada com você.