File writes via unvalidated storage filenames
Published Jan 4, 2022 · Updated Aug 4, 2024
Path traversal in Django 2.2 before 2.2.26, 3.2 before 3.2.11, and 4.0 before 4.0.1 allows attackers to write files outside storage roots. Storage.save() accepted a backend-returned name without revalidating it, while filename checks failed to normalize backslashes before inspecting path components. Exploitation requires an application to pass an attacker-controlled crafted filename directly to Storage.save(); the writable location and resulting impact depend on the storage backend and process permissions.
Summary
What happened
Path traversal in Django 2.2 before 2.2.26, 3.2 before 3.2.11, and 4.0 before 4.0.1 allows attackers to write files outside storage roots. Storage.save() accepted a backend-returned name without revalidating it, while filename checks failed to normalize backslashes before inspecting path components. Exploitation requires an application to pass an attacker-controlled crafted filename directly to Storage.save(); the writable location and resulting impact depend on the storage backend and process permissions.
The record
- CVE
- CVE-2021-45452
- Published
- Jan 4, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-22
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 4, 2022CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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