CVE-2013-1443: High severity djangoproject Django vulnerability

Published Sep 23, 2013
·
Updated

The authentication framework (django.contrib.auth) in Django 1.4.x before 1.4.8, 1.5.x before 1.5.4, and 1.6.x before 1.6 beta 4 allows remote attackers to cause a denial of service (CPU consumption) via a long password which is then hashed.

Affected Software

18 affected componentsFixes available
pip/Django>=1.5<1.5.4
1.5.4
pip/Django>=1.4<1.4.8
1.4.8
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.6-beta1
djangoproject Django=1.6-beta2
djangoproject Django=1.6-beta3
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

Event History

Sep 23, 2013
CVE Published
via MITRE·08:00 PM
Data Sourced
via MITRE·08:00 PM
Description
May 17, 2022
Advisory Published
via GitHub·04:53 AM

Frequently Asked Questions

1

What is the severity of CVE-2013-1443?

CVE-2013-1443 has a medium severity rating due to its potential to cause denial of service through excessive CPU usage.

2

How do I fix CVE-2013-1443?

To fix CVE-2013-1443, upgrade Django to version 1.4.8, 1.5.4, or newer.

3

Which versions of Django are affected by CVE-2013-1443?

CVE-2013-1443 affects Django versions 1.4.x before 1.4.8, 1.5.x before 1.5.4, and 1.6.x before 1.6 beta 4.

4

What type of attack can exploit CVE-2013-1443?

CVE-2013-1443 can be exploited through a denial of service attack by sending a long password that consumes CPU resources.

5

Is there a workaround for CVE-2013-1443?

There is no direct workaround for CVE-2013-1443; upgrading to the patched version is recommended.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203