CVE-2022-24840 json
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in django-s3file
published 4y ago modified 4mo ago also GHSA-4w8f-hjm9-xwgf , PYSEC-2022-208 , EUVD-2022-0084
- cvss
- 9.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.1%
- EPSS 2.1% chance of exploitation in 30 days, percentile 81%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- pypi django-s3file 5.5.1
- django-s3file_project django-s3file 5.5.1
Is CVE-2022-24840 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
2.07% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/codingjoe/django-s3file/security/advisories/GHSA-4w8f-hjm9-xwgf referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
| GitHub | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | django-s3file | <5.5.1 |
5.5.1 |
Affected products
- codingjoe django-s3file
Classification
References
-
github.com
/codingjoe/django-s3file/commit/68ccd2c621a40eb66fdd6af2be9d5fcc9c373318
web, patch, third-party-advisory
-
github.com
/codingjoe/django-s3file/security/advisories/GHSA-4w8f-hjm9-xwgf
web, exploit, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-24840
advisory
-
github.com
/codingjoe/django-s3file
package
-
github.com
/codingjoe/django-s3file/releases/tag/5.5.1
web
-
github.com
/pypa/advisory-database/tree/main/vulns/django-s3file/PYSEC-2022-208.yaml
web
Sources
- CVE List CVE-2022-24840
- GitHub Advisory GHSA-4w8f-hjm9-xwgf
- NVD CVE-2022-24840
- OSV PYSEC-2022-208
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.