| Name | CVE-2021-33026 |
| Description | 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 |
| Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
| Debian Bugs | 988916 |
The table below lists information on source packages.
| Source Package | Release | Version | Status |
|---|---|---|---|
| flask-caching (PTS) | bullseye | 1.9.0-1 | vulnerable |
| bookworm | 2.0.2-1 | vulnerable | |
| trixie, sid | 2.2.0-1 | vulnerable |
The information below is based on the following data on fixed versions.
| Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
|---|---|---|---|---|---|---|
| flask-caching | source | (unstable) | (unfixed) | unimportant | 988916 |
https://github.com/sh4nks/flask-caching/pull/209
Negligible security impact