| Name | CVE-2020-22083 |
| Description | 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 |
| Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
Vulnerable and fixed packages
The table below lists information on source packages.
| Source Package | Release | Version | Status |
|---|
| jsonpickle (PTS) | jessie | 0.8.0-1 | vulnerable |
| stretch | 0.9.3-2 | vulnerable |
| buster | 0.9.5-1 | vulnerable |
| bullseye | 1.2-1 | vulnerable |
| bookworm | 3.0.0+dfsg1-1 | vulnerable |
| trixie | 3.4.2+dfsg-1 | vulnerable |
| sid | 4.0.0+dfsg-1 | vulnerable |
The information below is based on the following data on fixed versions.
| Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
|---|
| jsonpickle | source | (unstable) | (unfixed) | unimportant | | |
Notes
CVE assigment seems bogus, jsonpickle clearly states "jsonpickle can execute arbitrary Python code.
Do not load jsonpickles from untrusted unauthenticated sources", so this works as expected