{"id":"CVE-2020-22083","details":"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","aliases":["GHSA-j66q-qmrc-89rx","PYSEC-2020-49"],"modified":"2026-04-02T05:08:30.611625Z","published":"2020-12-17T16:15:12.610Z","references":[{"type":"ADVISORY","url":"https://github.com/jsonpickle/jsonpickle/issues/332#issuecomment-747807494"},{"type":"ADVISORY","url":"https://access.redhat.com/security/cve/CVE-2020-22083"},{"type":"ADVISORY","url":"https://gist.github.com/j0lt-github/bb543e77a1a10c33cb56cf23d0837874"},{"type":"ADVISORY","url":"https://github.com/j0lt-github/python-deserialization-attack-payload-generator"},{"type":"ADVISORY","url":"https://github.com/jsonpickle/jsonpickle/issues/332"},{"type":"EVIDENCE","url":"https://versprite.com/blog/application-security/into-the-jar-jsonpickle-exploitation/"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://github.com/jsonpickle/jsonpickle","events":[{"introduced":"0"},{"last_affected":"632b9a9c8683fd6130855fe633768ff426b3acec"}],"database_specific":{"versions":[{"introduced":"0"},{"last_affected":"1.4.1"}]}}],"versions":["0.0.5","0.1.0","0.2.0","0.3.0","0.3.1","0.4.0","v0.5.0","v0.6.0","v0.6.1","v0.7.0","v0.7.1","v0.7.2","v0.8.0","v0.9.0","v0.9.1","v0.9.2","v0.9.3","v0.9.4","v0.9.5","v0.9.6","v1.0","v1.1","v1.2","v1.3","v1.4","v1.4.1"],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2020-22083.json"}}],"schema_version":"1.7.5","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"}]}