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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2014-0481US | medium4.3 | — | ||
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… | ||||
02
references
External citations — patches, advisories, analysis.
- http://lists.opensuse.org/opensuse-updates/2014-09/msg00023.htmlWEB
- http://secunia.com/advisories/59782ADVISORY
- http://secunia.com/advisories/61276ADVISORY
- http://secunia.com/advisories/61281ADVISORY
- http://www.debian.org/security/2014/dsa-3010ADVISORY
- https://github.com/advisories/GHSA-296w-6qhq-gf92ADVISORY
- https://www.djangoproject.com/weblog/2014/aug/20/security/ARTICLE
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan