CAPEC-586
Alerte pour un CAPEC
Stay informed of any changes for a specific CAPEC.
Description
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.
Informations
Prerequisites
The target application must unserialize data before validation.Mitigations
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. Use an allowlist of acceptable classes.
Implementation: Keep session state on the server, when possible.
Related Weaknesses
| Weakness Name | |
|---|---|
| Deserialization of Untrusted Data The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. |
References
REF-468
Deserialization of Untrusted DataSubmission
| Name | Organization | Date | Date Release |
|---|---|---|---|
| CAPEC Content Team | The MITRE Corporation |
Modifications
| Name | Organization | Date | Comment |
|---|---|---|---|
| CAPEC Content Team | The MITRE Corporation | Updated References, Related_Weaknesses | |
| CAPEC Content Team | The MITRE Corporation | Updated Mitigations | |
| CAPEC Content Team | The MITRE Corporation | Updated Mitigations |
2024©
tesweb SA
