Code execution via poisoned Pickle cache entry
Published May 13, 2021 · Updated Aug 3, 2024
Deserialization of untrusted data in Flask-Caching 1.10.1 and earlier allows attackers to execute Python code through a poisoned cache. The cache backends use Pickle to deserialize stored values, so loading a crafted entry invokes attacker-controlled Python object reconstruction. Exploitation requires arbitrary cache-write access, a colliding key, and an application read of the malicious entry; the maintainer considers that state already compromised.
Summary
What happened
Deserialization of untrusted data in Flask-Caching 1.10.1 and earlier allows attackers to execute Python code through a poisoned cache. The cache backends use Pickle to deserialize stored values, so loading a crafted entry invokes attacker-controlled Python object reconstruction. Exploitation requires arbitrary cache-write access, a colliding key, and an application read of the malicious entry; the maintainer considers that state already compromised.
The record
- CVE
- CVE-2021-33026
- Published
- May 13, 2021
- Updated
- Aug 3, 2024
- Vendor
- Pallets Ecosystem
- Product
- Flask-Caching
- Classifications
- CWE-502, CWE-269, T1059.006
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- May 13, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.10.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo