CRITICAL9.8
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
CVSS 2.0HIGH 7.5
CVSS:2.0/AV:N/AC:L/Au:N/C:P/I:P/A:PCVSS 3.xCRITICAL 9.8
CVSS:3.x/CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HReferences
- 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/