Django denial of service via file upload naming
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://www.debian.org/security/2014/dsa-3010WEB
- https://github.com/django/djangoPACKAGE
- https://github.com/django/django/commit/26cd48e166ac4d84317c8ee6d63ac52a87e8da99WEB
- https://github.com/django/django/commit/30042d475bf084c6723c6217a21598d9247a9c41WEB
- https://github.com/django/django/commit/dd0c3f4ee1a30c1a1e6055061c6ba6e58c6b54d1WEB
- https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2014-5.yamlWEB
- https://nvd.nist.gov/vuln/detail/CVE-2014-0481ADVISORY
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