CWE-579
J2EE Bad Practices: Non-serializable Object Stored in Session
Description
The product stores a non-serializable object as an HttpSession attribute, which can hurt reliability.
A J2EE application can make use of multiple JVMs in order to improve application reliability and performance. In order to make the multiple JVMs appear as a single application to the end user, the J2EE container can replicate an HttpSession object across multiple JVMs so that if one JVM becomes unavailable another can step in and take its place without disrupting the flow of the application. This is only possible if all session data is serializable, allowing the session to be duplicated between the JVMs.
Parent Weaknesses (ChildOf)
Common Consequences
Scope
Impact
Quality Degradation
Potential Mitigations
In order for session replication to work, the values the product stores as attributes in the session must implement the Serializable interface.
Applicable Platforms
Security Training
Train your team to recognize and prevent security threats with our comprehensive security awareness program.
Start TrainingVulnerability Scanning
Discover vulnerabilities in your applications and infrastructure before attackers do.
Scan Now