DjangoFramework / library · Djangoproject
CVE-2024-39614
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 · uneditedAn issue was discovered in Django 5.0 before 5.0.7 and 4.2 before 4.2.14. get_supported_language_variant() was subject to a potential denial-of-service attack when used with very long strings containing specific characters.
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 confidenceDjango's get_supported_language_variant() function, used for internationalization, is vulnerable to a denial-of-service attack. Attackers can exploit this by submitting very long strings containing specific characters, causing excessive computation or resource consumption when the function processes these language variant requests.
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
>= 4.2, < 4.2.14>= 5.0, < 5.0.7CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Django versionRun 'python -c "import django; print(django.get_version())"' or check your requirements/pip list for the django package versionAffected if The version is 4.2.x below 4.2.14, or 5.0.x below 5.0.7, or any 5.1.x version below the fixed release
-
Verify i18n is enabled in Django settingsInspect your Django settings.py and check if USE_I18N = True (the default) and that LANGUAGE_CODE is setAffected if Internationalization is enabled (USE_I18N is True) and language settings are configured
-
Identify if language variant requests are processedCheck application logs or code for calls to get_supported_language_variant() or similar i18n functions that accept user-supplied language codes as inputAffected if The application accepts language codes from user input (URL parameters, headers like Accept-Language, cookies, or form data) and passes them to Django's i18n functions
You are affected if you are running a vulnerable Django version (4.2.x below 4.2.14 or 5.0.x below 5.0.7) and your application has internationalization enabled and processes language codes from untrusted input.
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.2.145.0.7
Upgrade Django to version 5.0.7 or 4.2.14 or later. As a temporary mitigation, implement input validation to limit the length and character set of language codes submitted to the application.
Django 4.2.14 (for 4.2 branch) or Django 5.0.7 (for 5.0 branch)
- 1. Identify your current Django version by running: python -m django --version
- 2. Determine which Django branch you are using (4.2.x or 5.0.x)
- 3. If using Django 4.2.x: pip install --upgrade 'Django>=4.2.14,<5.0'
- 4. If using Django 5.0.x: pip install --upgrade 'Django>=5.0.7,<5.1'
- 5. Alternatively, install the specific fixed version directly: pip install Django==4.2.14 or pip install Django==5.0.7
- 6. Verify the upgrade was successful: python -m django --version
- 7. Run your test suite to ensure the application functions correctly after the upgrade
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
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-39614 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-39614 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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