CAPEC-586

Object Injection
Medium
High
Draft
2017-02-06
00h00 +00:00
2020-12-17
00h00 +00:00
CAPEC Mitre.org
Alerte pour un CAPEC
Stay informed of any changes for a specific CAPEC.
Notifications manage

Descriptions CAPEC

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 CAPEC

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

CWE-ID Weakness Name

CWE-502

 Deserialization of Untrusted Data
The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.

References

REF-468

Deserialization of Untrusted Data

Submission

Name Organization Date Date release
CAPEC Content Team The MITRE Corporation 2017-02-06 +00:00

Modifications

Name Organization Date Comment
CAPEC Content Team The MITRE Corporation 2018-07-31 +00:00 Updated References, Related_Weaknesses
CAPEC Content Team The MITRE Corporation 2020-07-30 +00:00 Updated Mitigations
CAPEC Content Team The MITRE Corporation 2020-12-17 +00:00 Updated Mitigations