Safety vulnerability ID: 35514
The information on this page was manually curated by our Cybersecurity Intelligence Team.
Django 1.4.14, 1.5.9, 1.6.6 and 1.7rc3 include a fix for CVE-2014-0481: 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.
Latest version: 5.1.3
A high-level Python web framework that encourages rapid development and clean, pragmatic design.
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.
CONFIRM:https://www.djangoproject.com/weblog/2014/aug/20/security/: https://www.djangoproject.com/weblog/2014/aug/20/security/
DEBIAN:DSA-3010: http://www.debian.org/security/2014/dsa-3010
SUSE:openSUSE-SU-2014:1132: http://lists.opensuse.org/opensuse-updates/2014-09/msg00023.html
SECUNIA:59782: http://secunia.com/advisories/59782
SECUNIA:61276: http://secunia.com/advisories/61276
SECUNIA:61281: http://secunia.com/advisories/61281
Scan your Python project for dependency vulnerabilities in two minutes
Scan your application