CWE-579 Non-serializable Object Stored in Session (J2EE)
Storing a non-serializable object in HttpSession breaks session replication and hurts reliability. Here is how CWE-579 happens and how to fix it.
Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
Storing a non-serializable object in HttpSession breaks session replication and hurts reliability. Here is how CWE-579 happens and how to fix it.
Class loaders are reserved for the EJB container. See why CWE-578 can compromise security and how to remove it.
An enterprise bean may be a socket client but not a server. See why CWE-577 breaks the EJB model and how to fix it.
Enterprise beans should not use java.io to reach the file system. See why CWE-576 breaks portability and the fix.
Enterprise beans must not drive a display or keyboard with AWT or Swing. See why CWE-575 breaks and how to fix it.
Enterprise beans must not use thread synchronization to coordinate instances. See why CWE-574 breaks portability and what to do instead.
CWE-573 covers code that calls an API, protocol or framework in ways its specification does not allow. Learn the pattern and how to avoid it.
Calling run() on a Thread runs the work in the caller's thread. See why CWE-572 is a bug and how to fix it with start().
A condition that is always true makes a branch unconditional and its else path dead. See how CWE-571 appears and how to fix it.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.