← Back
CVE-2020-22083
Vulnerability in jsonpickle (CVE-2020-22083)
Summary
vulnerability in jsonpickle (CVE-2020-22083). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `1.4.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2020-22083** has been found in jsonpickle.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade jsonpickle to **1.4.2** or later.
If unsure, ask your IT team or search "jsonpickle CVE-2020-22083" on the vendor's site.
CVE-2020-22083 (jsonpickle) —
Patched: `1.4.2` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (unclassified) exists in jsonpickle.
📍 Affected scope
jsonpickle — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.4.2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'jsonpickle' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'jsonpickle' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `jsonpickle` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade jsonpickle to 1.4.2ステージング環境で 1.4.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
jsonpickle
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.4.2"}]}]
References
- advisory https://github.com/advisories/GHSA-j66q-qmrc-89rx
- report https://github.com/jsonpickle/jsonpickle/issues/332
- report https://github.com/jsonpickle/jsonpickle/issues/332#issuecomment-747807494
- web https://gist.github.com/j0lt-github/bb543e77a1a10c33cb56cf23d0837874
- web https://github.com/j0lt-github/python-deserialization-attack-payload-generator
- web https://versprite.com/blog/application-security/into-the-jar-jsonpickle-exploitation/
- web https://access.redhat.com/security/cve/CVE-2020-22083