Flask Caching
Approved changes feed: RSS · Atom
cpe:2.3:a:flask-caching_project:flask-caching:*:*:*:*:*:flask:*:*part: a version: * update: *
| Vendor | Flask Caching Project (b172df65-36f4-551a-8f02-20a5a906c882) |
|---|---|
| Product | Flask Caching (37cec9c0-53a5-5090-bab9-a0425c81a981) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | flask |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2021-33026 |
vulnerable | 2026-06-08 05:32:08.530956 |
Details available
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
Published: 2021-05-13T22:51:20.000Z
Updated: 2024-08-03T23:42:19.075Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.