CVE-2020-22083
- Source
- https://cve.org/CVERecord?id=CVE-2020-22083
- Import Source
- https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2020-22083.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/CVE-2020-22083
- Aliases
- Downstream
- Published
- 2020-12-17T16:15:12.610Z
- Modified
- 2026-04-11T20:41:24.093565Z
- Severity
-
- 9.8 (Critical) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H CVSS Calculator
- Summary
- [none]
- 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
- References
-
- 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/
Affected packages
Git / github.com/jsonpickle/jsonpickle
Affected ranges
- Type
- GIT
- Repo
- https://github.com/jsonpickle/jsonpickle
- Events
-
Introduced0 Unknown introduced commit / All previous commits are affectedLast affected
- Database specific
{ "source": "CPE_FIELD", "cpe": "cpe:2.3:a:jsonpickle_project:jsonpickle:*:*:*:*:*:*:*:*", "extracted_events": [ { "introduced": "0" }, { "last_affected": "1.4.1" } ] }