{"api_version":"1","generated_at":"2026-07-24T18:47:08+00:00","cve":"CVE-2020-22083","urls":{"html":"https://cve.report/CVE-2020-22083","api":"https://cve.report/api/cve/CVE-2020-22083.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2020-22083","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2020-22083"},"summary":{"title":"CVE-2020-22083","description":"** DISPUTED ** 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.","state":"PUBLIC","assigner":"cve@mitre.org","published_at":"2020-12-17 16:15:00","updated_at":"2023-11-07 03:19:00"},"problem_types":["CWE-502"],"metrics":[],"references":[{"url":"https://github.com/jsonpickle/jsonpickle/issues/332#issuecomment-747807494","name":"https://github.com/jsonpickle/jsonpickle/issues/332#issuecomment-747807494","refsource":"MISC","tags":["Third Party Advisory"],"title":"Jsonpickle decode() function unsafely form objects that can lead to Remote code execution · Issue #332 · jsonpickle/jsonpickle · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://github.com/j0lt-github/python-deserialization-attack-payload-generator","name":"https://github.com/j0lt-github/python-deserialization-attack-payload-generator","refsource":"MISC","tags":["Third Party Advisory"],"title":"GitHub - j0lt-github/python-deserialization-attack-payload-generator: Peas create serialized payload for deserialization RCE attack on python driven applications where pickle ,pyYAML, ruamel.yaml or jsonpickle module is used for deserialization of serialized data. I will update it with more attack vectors to targets other modules.","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://versprite.com/blog/application-security/into-the-jar-jsonpickle-exploitation/","name":"https://versprite.com/blog/application-security/into-the-jar-jsonpickle-exploitation/","refsource":"MISC","tags":["Exploit","Third Party Advisory"],"title":"JSON Pickle Exploitation | Python's Pickle Module - Target for Exploitation","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://github.com/jsonpickle/jsonpickle/issues/332","name":"https://github.com/jsonpickle/jsonpickle/issues/332","refsource":"MISC","tags":["Third Party Advisory"],"title":"Jsonpickle decode() function unsafely form objects that can lead to Remote code execution · Issue #332 · jsonpickle/jsonpickle · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://access.redhat.com/security/cve/CVE-2020-22083","name":"https://access.redhat.com/security/cve/CVE-2020-22083","refsource":"MISC","tags":["Third Party Advisory"],"title":"Red Hat Customer Portal - Access to 24x7 support and knowledge","mime":"text/html","httpstatus":"200","archivestatus":"404"},{"url":"https://gist.github.com/j0lt-github/bb543e77a1a10c33cb56cf23d0837874","name":"https://gist.github.com/j0lt-github/bb543e77a1a10c33cb56cf23d0837874","refsource":"MISC","tags":["Third Party Advisory"],"title":"jsonpickle 1.4.2 vulnerable to RCE · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://www.cve.org/CVERecord?id=CVE-2020-22083","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2020-22083","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[{"cve_year":"2020","cve_id":"22083","vulnerable":"1","versionEndIncluding":"1.4.1","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"jsonpickle_project","cpe5":"jsonpickle","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"}],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[{"cve":"CVE-2020-22083","qid":"997082","title":"Python (Pip) Security Update for jsonpickle (GHSA-j66q-qmrc-89rx)"}]},"source_records":{"cve_program":{"CVE_data_meta":{"ASSIGNER":"cve@mitre.org","ID":"CVE-2020-22083","STATE":"PUBLIC"},"affects":{"vendor":{"vendor_data":[{"product":{"product_data":[{"product_name":"n/a","version":{"version_data":[{"version_value":"n/a"}]}}]},"vendor_name":"n/a"}]}},"data_format":"MITRE","data_type":"CVE","data_version":"4.0","description":{"description_data":[{"lang":"eng","value":"** DISPUTED ** 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."}]},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"n/a"}]}]},"references":{"reference_data":[{"url":"https://github.com/j0lt-github/python-deserialization-attack-payload-generator","refsource":"MISC","name":"https://github.com/j0lt-github/python-deserialization-attack-payload-generator"},{"url":"https://versprite.com/blog/application-security/into-the-jar-jsonpickle-exploitation/","refsource":"MISC","name":"https://versprite.com/blog/application-security/into-the-jar-jsonpickle-exploitation/"},{"refsource":"MISC","name":"https://github.com/jsonpickle/jsonpickle/issues/332","url":"https://github.com/jsonpickle/jsonpickle/issues/332"},{"refsource":"MISC","name":"https://gist.github.com/j0lt-github/bb543e77a1a10c33cb56cf23d0837874","url":"https://gist.github.com/j0lt-github/bb543e77a1a10c33cb56cf23d0837874"},{"refsource":"MISC","name":"https://github.com/jsonpickle/jsonpickle/issues/332#issuecomment-747807494","url":"https://github.com/jsonpickle/jsonpickle/issues/332#issuecomment-747807494"},{"refsource":"MISC","name":"https://access.redhat.com/security/cve/CVE-2020-22083","url":"https://access.redhat.com/security/cve/CVE-2020-22083"}]}},"nvd":{"publishedDate":"2020-12-17 16:15:00","lastModifiedDate":"2023-11-07 03:19:00","problem_types":["CWE-502"],"metrics":{"baseMetricV3":{"cvssV3":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH","baseScore":9.8,"baseSeverity":"CRITICAL"},"exploitabilityScore":3.9,"impactScore":5.9},"baseMetricV2":{"cvssV2":{"version":"2.0","vectorString":"AV:N/AC:L/Au:N/C:P/I:P/A:P","accessVector":"NETWORK","accessComplexity":"LOW","authentication":"NONE","confidentialityImpact":"PARTIAL","integrityImpact":"PARTIAL","availabilityImpact":"PARTIAL","baseScore":7.5},"severity":"HIGH","exploitabilityScore":10,"impactScore":6.4,"acInsufInfo":false,"obtainAllPrivilege":false,"obtainUserPrivilege":false,"obtainOtherPrivilege":false,"userInteractionRequired":false}},"configurations":{"CVE_data_version":"4.0","nodes":[{"operator":"OR","children":[],"cpe_match":[{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:jsonpickle_project:jsonpickle:*:*:*:*:*:*:*:*","versionEndIncluding":"1.4.1","cpe_name":[]}]}]}},"legacy_mitre":{"record":{"CveYear":"2020","CveId":"22083","Ordinal":"183492","Title":"CVE-2020-22083","CVE":"CVE-2020-22083","Year":"2020"},"notes":[{"CveYear":"2020","CveId":"22083","Ordinal":"1","NoteData":"** DISPUTED ** 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.","Type":"Description","Title":null},{"CveYear":"2020","CveId":"22083","Ordinal":"2","NoteData":"2020-12-17","Type":"Other","Title":"Published"},{"CveYear":"2020","CveId":"22083","Ordinal":"3","NoteData":"2020-12-22","Type":"Other","Title":"Modified"}]}}}