Common Attack Pattern Enumeration and Classification
A Community Resource for Identifying and Understanding Attacks
An adversary attempts to exploit an application by injecting additional, malicious content during its processing of serialized objects. Developers leverage serialization in order to convert data or state into a static, binary format for saving to disk or transferring over a network. These objects are then deserialized when needed to recover the data/state. By injecting a malformed object into a vulnerable application, an adversary can potentially compromise the application by manipulating the deserialization process. This can result in a number of unwanted outcomes, including remote code execution.
Implementation: Validate object before deserialization process
Design: Limit which types can be deserialized.
Implementation: Avoid having unnecessary types or gadgets available that can be leveraged for malicious ends. Whitelist acceptable classes.
Implementation: Keep session state on the server, when possible.
[R.17.1] [REF-2] "CWE-502: Deserialization of Untrusted Data". MITRE. January 2017.
[R.17.1] [REF-2] "Deserialization of Untrusted Data". OWASP. January 2017.
More information is available — Please select a different filter.