Skip to content
Fencer Intel
high 7.5

CVE-2013-1443 json

Django Denial of Service Vulnerability in the authentication framework

published 13y ago modified 4mo ago also GHSA-4c42-4rxm-x6qf , PYSEC-2013-18 , EUVD-2013-0006

cvss
7.5
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
2.7%
EPSS 2.7% chance of exploitation in 30 days, percentile 86%
public exploits
0
none known

Summary

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.

Patch / fix

  • pypi django 1.4.8, 1.5.4
  • python-django Debian 14, Debian 13, Debian 12 1.5.4-1

debian advisories DEBIAN-CVE-2013-1443

Is CVE-2013-1443 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2013-1443 updated cvss 4.3

python-django: DoS via large passwords

  • Red Hat Subscription Asset Manager Django
    affected: no fix planned “Will not fix”
  • Red Hat OpenStack Platform 3 Django14
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.74% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
pypi django
>=1.4, <1.4.8
>=1.5, <1.5.4
1.4.8
1.5.4

Classification

Weakness
  • CWE-287 Improper Authentication
  • CWE-400 Uncontrolled Resource Consumption
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.