Django S3File
Approved changes feed: RSS · Atom
cpe:2.3:a:django-s3file_project:django-s3file:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Django S3File Project (d2110e36-5e52-5bc1-b6e5-6005e1c1dc3e) |
|---|---|
| Product | Django S3File (93b132c3-9111-5364-bb43-f650492d4ba0) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from purl2cpe mapping
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/codingjoe/django-s3file |
purl2cpe | 2026-06-01 10:13:24.825706 |
pkg:opensuse/python-django-s3file |
purl2cpe | 2026-06-01 10:13:24.825709 |
pkg:pypi/django-s3file |
purl2cpe | 2026-06-01 10:13:24.825712 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2022-24840 |
vulnerable | 2026-06-08 05:41:44.739733 |
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in django-s3file
CRITICAL (9.1)
django-s3file is a lightweight file upload input for Django and Amazon S3 . In versions prior to 5.5.1 it was possible to traverse the entire AWS S3 bucket and in most cases to access or delete files. If the `AWS_LOCATION` setting was set, traversal was limited to that location only. The issue was discovered by the maintainer. There were no reports of the vulnerability being known to or exploited by a third party, prior to the release of the patch. The vulnerability has been fixed in version 5.5.1 and above. There is no feasible workaround. We must urge all users to immediately updated to a patched version.
Published: 2022-06-06T19:10:11.000Z
Updated: 2025-04-22T17:54:56.216Z |
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.