Description
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 (6)
Core 6
Core References
Third Party Advisory x_refsource_misc
https://github.com/j0lt-github/python-deserialization-attack-payload-generator
Exploit, Third Party Advisory x_refsource_misc
https://versprite.com/blog/application-security/into-the-jar-jsonpickle-exploitation/
Third Party Advisory x_refsource_misc
https://github.com/jsonpickle/jsonpickle/issues/332
Third Party Advisory x_refsource_misc
https://gist.github.com/j0lt-github/bb543e77a1a10c33cb56cf23d0837874
Third Party Advisory x_refsource_misc
https://github.com/jsonpickle/jsonpickle/issues/332#issuecomment-747807494
Third Party Advisory x_refsource_misc
https://access.redhat.com/security/cve/CVE-2020-22083
Scores
CVSS v3
9.8
EPSS
0.0470
EPSS Percentile
89.4%
Attack Vector
NETWORK
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Details
CWE
CWE-502
Status
published
Products (2)
jsonpickle_project/jsonpickle
< 1.4.1
pypi/jsonpickle
0PyPI
Published
Dec 17, 2020
Tracked Since
Feb 18, 2026