The Flask-Caching extension through 1.10.1 for Flask relies on Pickle for serialization, which may lead to remote code execution or local privilege escalation. If an attacker gains access to cache storage (e.g., filesystem, Memcached, Redis, etc.), they can construct a crafted payload, poison the cache, and execute Python code. NOTE: a third party indicates that exploitation is extremely unlikely unless the machine is already compromised; in other cases, the attacker would be unable to write their payload to the cache and generate the required collision
References
| Link | Resource |
|---|---|
| https://github.com/pallets-eco/flask-caching/pull/209#issuecomment-1136397937 | Issue Tracking Patch Third Party Advisory |
| https://github.com/sh4nks/flask-caching/pull/209 | Patch Third Party Advisory |
Configurations
History
07 Nov 2023, 03:35
| Type | Values Removed | Values Added |
|---|---|---|
| Summary | The Flask-Caching extension through 1.10.1 for Flask relies on Pickle for serialization, which may lead to remote code execution or local privilege escalation. If an attacker gains access to cache storage (e.g., filesystem, Memcached, Redis, etc.), they can construct a crafted payload, poison the cache, and execute Python code. NOTE: a third party indicates that exploitation is extremely unlikely unless the machine is already compromised; in other cases, the attacker would be unable to write their payload to the cache and generate the required collision |
Information
Published : 2021-05-13 23:15
Updated : 2024-08-04 00:15
NVD link : CVE-2021-33026
Mitre link : CVE-2021-33026
CVE.ORG link : CVE-2021-33026
JSON object : View
Products Affected
flask-caching_project
- flask-caching
CWE
CWE-502
Deserialization of Untrusted Data