CVE-2014-0481: Django denial of service via file upload naming
(updated )
The default configuration for the file upload handling system in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 uses a sequential file name generation process when a file with a conflicting name is uploaded, which allows remote attackers to cause a denial of service (CPU consumption) by unloading a multiple files with the same name.
References
- github.com/advisories/GHSA-296w-6qhq-gf92
- github.com/django/django
- github.com/django/django/commit/26cd48e166ac4d84317c8ee6d63ac52a87e8da99
- github.com/django/django/commit/30042d475bf084c6723c6217a21598d9247a9c41
- github.com/django/django/commit/dd0c3f4ee1a30c1a1e6055061c6ba6e58c6b54d1
- github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2014-5.yaml
- nvd.nist.gov/vuln/detail/CVE-2014-0481
- www.djangoproject.com/weblog/2014/aug/20/security
Code Behaviors & Features
Detect and mitigate CVE-2014-0481 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →