Deserialization in Jsonpickle Project
CVE-2020-22083
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
Vulnerability class: Insecure Deserialization
Published · last modified .
CVSS v3 metric
CVSS v3 base score 9.8 (Critical). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
EPSS exploit prediction
EPSS 0.066, 94.0th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 1 other repository (fkie-cad/nvd-json-data-feeds). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- github.com/j0lt-github/python-deserialization-attack-payload-generator (Third Party Advisory)
- versprite.com/blog/application-security/into-the-jar-jsonpickle-exploitation/ (Exploit, Third Party Advisory)
- github.com/jsonpickle/jsonpickle/issues/332 (Third Party Advisory)
- gist.github.com/j0lt-github/bb543e77a1a10c33cb56cf23d0837874 (Third Party Advisory)
- github.com/jsonpickle/jsonpickle/issues/332 (Third Party Advisory)
- access.redhat.com/security/cve/CVE-2020-22083 (Third Party Advisory)