The product stores a non-serializable object as an HttpSession attribute, which can hurt reliability.
View on MITREA 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.
In order for session replication to work, the values the product stores as attributes in the session must implement the Serializable interface.
No detection method information available for this CWE.
The following class adds itself to the session, but because it is not serializable, the session can no longer be replicated.
CWE-579: J2EE Bad Practices: Non-serializable Object Stored in Session is a Common Weakness Enumeration (CWE) entry maintained by MITRE. 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.
If exploited, CWE-579 (J2EE Bad Practices: Non-serializable Object Stored in Session) it can compromise Other, leading to outcomes such as Quality Degradation.
Recommended mitigations for CWE-579 include: In order for session replication to work, the values the product stores as attributes in the session must implement the Serializable interface.
CWE-579 commonly affects Java. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.
A CWE (Common Weakness Enumeration) like CWE-579 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.