Treeio through 2.0 Insecure Deserialization RCE via Admin-Editable Pickle Fields
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| treeio | treeio | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Treeio | Treeio |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.557% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Treeio
Treeio treeio |
|
| Vendors & Products |
Treeio
Treeio treeio |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Treeio through 2.0 contains an insecure deserialization vulnerability in UpdateRecord.get_format_strings and ModuleSetting.loads that allows staff users to execute code via unverified pickle data. Attackers can store a crafted base64 pickle payload in an UpdateRecord format_strings field through the Django admin, executing Python code as the web server user when news feeds render. | |
| Title | Treeio through 2.0 Insecure Deserialization RCE via Admin-Editable Pickle Fields | |
| Weaknesses | CWE-502 | |
| References |
|
|
| Metrics |
cvssV3_1
|