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.
Metrics
Affected Vendors & Products
Advisories
Source | ID | Title |
---|---|---|
![]() |
DLA-65-1 | python-django security update |
![]() |
DSA-3010-1 | python-django security update |
![]() |
EUVD-2014-0013 | 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. |
![]() |
GHSA-296w-6qhq-gf92 | Django denial of service via file upload naming |
![]() |
USN-2347-1 | Django vulnerabilities |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
No history.

Status: PUBLISHED
Assigner: debian
Published:
Updated: 2024-08-06T09:20:18.410Z
Reserved: 2013-12-19T00:00:00
Link: CVE-2014-0481

No data.

Status : Deferred
Published: 2014-08-26T14:55:05.250
Modified: 2025-04-12T10:46:40.837
Link: CVE-2014-0481


No data.