dbcve.org
DjangoFramework / library · Djangoproject

CVE-2024-39329

MEDIUM · 5.3 CVSS v3.1 Published 2024-07-10
Fix available
A fix is available. Upgrade to 4.2.14 / 5.0.7 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An issue was discovered in Django 5.0 before 5.0.7 and 4.2 before 4.2.14. The django.contrib.auth.backends.ModelBackend.authenticate() method allows remote attackers to enumerate users via a timing attack involving login requests for users with an unusable password.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A timing attack vulnerability in Django's ModelBackend authentication allows remote attackers to enumerate valid usernames by measuring response times on login requests. When a user has an 'unusable password' (e.g., disabled account, no password set), the authentication check returns faster than for valid users with usable passwords, enabling attackers to discover valid usernames through repeated timing measurements.

MitigationUpgrade Django to version 5.0.7 or 4.2.14 or later, which includes the fix to normalize authentication timing. Additionally, consider rate limiting login endpoints and monitoring for anomalous authentication patterns.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DjangoFramework / library
Affected:>= 4.2, < 4.2.14>= 5.0, < 5.0.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Django version
    Run 'python -c "import django; print(django.get_version())"' or check your requirements/pip list for Django version
    Affected if Version is 4.2.x below 4.2.14 OR 5.0.x below 5.0.7
  2. Verify ModelBackend is configured
    Check your Django settings file for AUTHENTICATION_BACKENDS. Look for 'django.contrib.auth.backends.ModelBackend' in the list
    Affected if ModelBackend is in the configured authentication backends (this is the default)
  3. Identify users with unusable passwords
    Run: python manage.py shell -c "from django.contrib.auth import get_user_model; User = get_user_model(); unusable = User.objects.filter(password__isnull=True).count(); print(f'Users with unusable password: {unusable}')"
    Affected if Any users exist with unusable passwords (password set to None or unusable password hash)
  4. Check if password hashers use constant-time comparison
    Inspect the PASSWORD_HASHERS setting in settings.py - the fix involves using constant-time comparison in password verification
    Affected if Using default password hashers without constant-time comparison in authentication flow

You are affected if Django version is below 4.2.14 or below 5.0.7, ModelBackend is your authentication backend, and any user accounts exist in the system with unusable passwords that could be enumerated via timing measurements.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.2.14 / 5.0.7 or later
Fixed in 4.2.145.0.7
Interim mitigation

Upgrade Django to version 5.0.7 or 4.2.14 or later, which includes the fix to normalize authentication timing. Additionally, consider rate limiting login endpoints and monitoring for anomalous authentication patterns.

Recommended fix High confidence

Django 4.2.14 (for 4.2.x branch) or Django 5.0.7 (for 5.0.x branch)

  1. Determine your current Django version by running `python -c "import django; print(django.get_version())"`
  2. Identify which release branch you are on (4.2.x or 5.0.x)
  3. If on Django 4.2.x: run `pip install --upgrade 'Django>=4.2.14,<5.0'`
  4. If on Django 5.0.x: run `pip install --upgrade 'Django>=5.0.7,<5.1'`
  5. Verify the upgrade was successful by running the version check again
  6. Test authentication flows in your application to confirm the fix works correctly
Caveat Standard Django upgrade considerations apply - review the release notes for any deprecation warnings or breaking changes between your current version and the target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Django Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,288.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-39329 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-39329 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data