jsonpickle up to 1.4.1 decode deserialization ⚔ [Disputed]
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.7 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as critical has been discovered in jsonpickle up to 1.4.1. This impacts the function decode. Such manipulation leads to deserialization.
This vulnerability is listed as CVE-2020-22083. The attack may be performed from remote. In addition, an exploit is available.
The actual existence of this vulnerability is currently in question.
A patch should be applied to remediate this issue.
Details
A vulnerability, which was classified as critical, has been found in jsonpickle up to 1.4.1. Affected by this issue is the function decode. The manipulation with an unknown input leads to a deserialization vulnerability. Using CWE to declare the problem leads to CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. Impacted is confidentiality, integrity, and availability. CVE summarizes:
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
The weakness was presented 12/18/2020. The advisory is available at versprite.com. This vulnerability is handled as CVE-2020-22083. Technical details as well as a public exploit are known.
The exploit is available at github.com. It is declared as proof-of-concept. The real existence of this vulnerability is still doubted at the moment.
Applying a patch is able to eliminate this problem. The bugfix is ready for download at gist.github.com.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.0VulDB Meta Temp Score: 7.7
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: DeserializationCWE: CWE-502 / CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Patch: gist.github.com
Timeline
12/18/2020 🔍12/18/2020 🔍
08/04/2024 🔍
Sources
Product: github.comAdvisory: versprite.com
Status: Confirmed
Confirmation: 🔍
Disputed: 🔍
CVE: CVE-2020-22083 (🔍)
GCVE (CVE): GCVE-0-2020-22083
GCVE (VulDB): GCVE-100-166538
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 12/18/2020 06:57Updated: 08/04/2024 18:07
Changes: 12/18/2020 06:57 (41), 08/04/2024 18:07 (36)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.