CVE-2022-24840
If the `AWS_LOCATION` setting was set, traversal was limited to that location only.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (2.04%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
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.
- CVSS 3.1
- 9.8 CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- EPSS
- 2.04% probability · 80th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-22
- Affected
- django-s3file project/django-s3file
- Source
- security-advisories@github.com
References
- https://github.com/codingjoe/django-s3file/commit/68ccd2c621a40eb66fdd6af2be9d5fcc9c373318Patch, Third Party Advisory
- https://github.com/codingjoe/django-s3file/security/advisories/GHSA-4w8f-hjm9-xwgfExploit, Third Party Advisory
- https://github.com/codingjoe/django-s3file/commit/68ccd2c621a40eb66fdd6af2be9d5fcc9c373318Patch, Third Party Advisory
- https://github.com/codingjoe/django-s3file/security/advisories/GHSA-4w8f-hjm9-xwgfExploit, Third Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.