CVE-2020-22083

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

Weakness

The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.

Affected Software

Potential Mitigations

• Make fields transient to protect them from deserialization.
• An attempt to serialize and then deserialize a class containing transient fields will result in NULLs where the transient data should be. This is an excellent way to prevent time, environment-based, or sensitive variables from being carried over and used improperly.

Related Attack Patterns

• https://cwe.mitre.org/data/definitions/586.html

References

• https://access.redhat.com/security/cve/CVE-2020-22083
• https://gist.github.com/j0lt-github/bb543e77a1a10c33cb56cf23d0837874
• https://github.com/j0lt-github/python-deserialization-attack-payload-generator
• https://github.com/jsonpickle/jsonpickle/issues/332
• https://github.com/jsonpickle/jsonpickle/issues/332#issuecomment-747807494
• https://versprite.com/blog/application-security/into-the-jar-jsonpickle-exploitation/
• https://access.redhat.com/security/cve/CVE-2020-22083
• https://gist.github.com/j0lt-github/bb543e77a1a10c33cb56cf23d0837874
• https://github.com/j0lt-github/python-deserialization-attack-payload-generator
• https://github.com/jsonpickle/jsonpickle/issues/332
• https://github.com/jsonpickle/jsonpickle/issues/332#issuecomment-747807494
• https://versprite.com/blog/application-security/into-the-jar-jsonpickle-exploitation/