Vulnerability advisory
CVE-2024-39330
Also known as BIT-django-2024-39330GHSA-9jmf-237g-qf46PYSEC-2024-58
Severity
- CVSS 3.x
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Affected versions
Repository
| Affected commits | Fixed by commit |
|---|---|
| GIT github.com/django/django ↗ | |
| 97aa3b7f08f51669e118f3af5ca91026e39664c3 to before 98cf264c9cb0561e4ec305a621e9d58116e44aef | 98cf264c9cb0561e4ec305a621e9d58116e44aef |
| 52821001bb62b764d73e63812133f199b8fef9eb to before deec9b933ee8496274e4c53217a38f31cb59a27f | deec9b933ee8496274e4c53217a38f31cb59a27f |
Description
An issue was discovered in Django 5.0 before 5.0.7 and 4.2 before 4.2.14. Derived classes of the django.core.files.storage.Storage base class, when they override generate_filename() without replicating the file-path validations from the parent class, potentially allow directory traversal via certain inputs during a save() call. (Built-in Storage sub-classes are unaffected.)
References
- Webdocs.djangoproject.com/en/dev/releases/security/ ↗
- Webgroups.google.com/forum/#%21forum/django-announce ↗
- Advisorygithub.com/CVEProject/cvelistV5/tree/main/cves/2024/39xxx/CVE-2024-39330.json ↗
- Advisorynvd.nist.gov/vuln/detail/CVE-2024-39330 ↗
- Advisorysecurity.netapp.com/advisory/ntap-20240808-0005/ ↗
- ARTICLEwww.djangoproject.com/weblog/2024/jul/09/security-releases/ ↗