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
References
Link | Resource |
---|---|
https://access.redhat.com/security/cve/CVE-2020-22083 | Third Party Advisory |
https://gist.github.com/j0lt-github/bb543e77a1a10c33cb56cf23d0837874 | Third Party Advisory |
https://github.com/j0lt-github/python-deserialization-attack-payload-generator | Third Party Advisory |
https://github.com/jsonpickle/jsonpickle/issues/332 | Third Party Advisory |
https://github.com/jsonpickle/jsonpickle/issues/332#issuecomment-747807494 | Third Party Advisory |
https://versprite.com/blog/application-security/into-the-jar-jsonpickle-exploitation/ | Exploit Third Party Advisory |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: mitre
Published: 2020-12-17T15:15:54
Updated: 2020-12-22T13:56:10
Reserved: 2020-08-13T00:00:00
Link: CVE-2020-22083
JSON object: View
NVD Information
Status : Modified
Published: 2020-12-17T16:15:12.610
Modified: 2024-05-17T01:45:20.900
Link: CVE-2020-22083
JSON object: View
Redhat Information
No data.
CWE