jsonpickle through 1.4.1 allows remote code execution during deserialization of a malicious payload through the decode() function. Note: It has been argued that this is expected and clearly documented behaviour. pickle is known to be capable of causing arbitrary code execution, and must not be used with un-trusted data
The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Jsonpickle | Jsonpickle_project | * | 1.4.1 (including) |
| Jsonpickle | Ubuntu | bionic | * |
| Jsonpickle | Ubuntu | groovy | * |
| Jsonpickle | Ubuntu | hirsute | * |
| Jsonpickle | Ubuntu | impish | * |
| Jsonpickle | Ubuntu | kinetic | * |
| Jsonpickle | Ubuntu | lunar | * |
| Jsonpickle | Ubuntu | mantic | * |
| Jsonpickle | Ubuntu | trusty | * |
| Jsonpickle | Ubuntu | xenial | * |
It is often convenient to serialize objects for communication or to save them for later use. However, deserialized data or code can often be modified without using the provided accessor functions if it does not use cryptography to protect itself. Furthermore, any cryptography would still be client-side security – which is a dangerous security assumption. Data that is untrusted can not be trusted to be well-formed. When developers place no restrictions on “gadget chains,” or series of instances and method invocations that can self-execute during the deserialization process (i.e., before the object is returned to the caller), it is sometimes possible for attackers to leverage them to perform unauthorized actions, like generating a shell.