CVE-2020-22083PYSEC-2020-49GHSA-J66Q-QMRC-89RX
jsonpickle through 1.4.1 allows remote code execution during deserialization of a malicious payload through the decode() function.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.4.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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
Timeline
- CVE published
- Record last updated
Affected versions
- n/a n/a
Version range not reported
- jsonpicklePyPI
fixed in 1.4.2
- jsonpicklePyPI
through 1.4.2