** DISPUTED ** 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/sh4nks/flask-caching/pull/209 | Patch Third Party Advisory |
https://github.com/pallets-eco/flask-caching/pull/209#issuecomment-1136397937 |
Configurations
Information
Published : 2021-05-13 16:15
Updated : 2022-09-16 16:15
NVD link : CVE-2021-33026
Mitre link : CVE-2021-33026
JSON object : View
CWE
CWE-502
Deserialization of Untrusted Data
Products Affected
flask-caching_project
- flask-caching