high
7.5
CWE
400 399
Advisory Published
Advisory Published
Updated

CVE-2014-0481

First published: Tue Aug 26 2014(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.

Credit: security@debian.org

Affected SoftwareAffected VersionHow to fix
pip/Django>=1.5<1.5.9
1.5.9
pip/django>=1.6<1.6.6
1.6.6
pip/django<1.4.14
1.4.14
openSUSE=13.1
openSUSE=12.3
djangoproject Django<=1.4.13
djangoproject Django=1.4
djangoproject Django=1.4.1
djangoproject Django=1.4.2
djangoproject Django=1.4.4
djangoproject Django=1.4.5
djangoproject Django=1.4.6
djangoproject Django=1.4.7
djangoproject Django=1.4.8
djangoproject Django=1.4.9
djangoproject Django=1.4.10
djangoproject Django=1.4.11
djangoproject Django=1.4.12
djangoproject Django=1.5
djangoproject Django=1.5-alpha
djangoproject Django=1.5-beta
djangoproject Django=1.5.1
djangoproject Django=1.5.2
djangoproject Django=1.5.3
djangoproject Django=1.5.4
djangoproject Django=1.5.5
djangoproject Django=1.5.6
djangoproject Django=1.5.7
djangoproject Django=1.5.8
djangoproject Django=1.7-beta1
djangoproject Django=1.7-beta2
djangoproject Django=1.7-beta3
djangoproject Django=1.7-beta4
djangoproject Django=1.7-rc1
djangoproject Django=1.7-rc2
djangoproject Django=1.6
djangoproject Django=1.6-beta1
djangoproject Django=1.6-beta2
djangoproject Django=1.6-beta3
djangoproject Django=1.6-beta4
djangoproject Django=1.6.1
djangoproject Django=1.6.2
djangoproject Django=1.6.3
djangoproject Django=1.6.4
djangoproject Django=1.6.5
Debian GNU/Linux=7.0

Remedy

https://www.djangoproject.com/weblog/2014/aug/20/security/

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2014-0481?

    CVE-2014-0481 has a medium severity rating due to its potential to allow unauthorized file uploads through name conflicts.

  • How do I fix CVE-2014-0481?

    To fix CVE-2014-0481, upgrade Django to versions 1.5.9, 1.6.6, or 1.4.14 and later.

  • What versions of Django are affected by CVE-2014-0481?

    CVE-2014-0481 affects Django versions 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.

  • Who is affected by CVE-2014-0481?

    Users of affected versions of Django who implement file upload features are vulnerable to CVE-2014-0481.

  • Is there a workaround for CVE-2014-0481?

    No official workarounds have been provided for CVE-2014-0481, and upgrading is strongly recommended.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203