CWEweakness

CWE-579 J2EE Bad Practices: Non-serializable Object Stored in Session

Official page ↗
Abstraction
Variant
Structure
Simple
Status
Draft
Languages
Java
CWE version
5.0

Description

The product stores a non-serializable object as an HttpSession attribute.

Common consequences

• Other: Quality Degradation, Reduce Reliability

Potential mitigations

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

Detection methods

• Automated Static Analysis: 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.)

Related

Child of · CWE (1)

  • CWE-573 Improper Following of Specification by Caller weakness

Referenced by OWASP · mapped cwe (1)