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 |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: mitre
Published: 2021-05-13T22:51:20
Updated: 2022-09-16T22:55:27
Reserved: 2021-05-13T00:00:00
Link: CVE-2021-33026
JSON object: View
NVD Information
Status : Modified
Published: 2021-05-13T23:15:07.367
Modified: 2024-05-17T01:57:47.060
Link: CVE-2021-33026
JSON object: View
Redhat Information
No data.
CWE