DjangoFramework / library · Djangoproject
CVE-2024-45230
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.1 before 5.1.1, 5.0 before 5.0.9, and 4.2 before 4.2.16. The urlize() and urlizetrunc() template filters are subject to a potential denial-of-service attack via very large inputs with a specific sequence of 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 urlize() and urlizetrunc() template filters, which convert URLs in text to clickable HTML links, contain a denial-of-service vulnerability. Attackers can trigger excessive CPU consumption or hang the server by submitting very large inputs containing a specific sequence of characters to these filters.
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.0, < 4.2.16>= 5.0, < 5.0.9= 5.1CVSS 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.txt/pyproject.toml for the Django versionAffected if Version is 4.2.0-4.2.15, 5.0.0-5.0.8, or 5.1.0-5.1.0 (exact version 5.1)
-
Identify usage of urlize template filterSearch your codebase for '|urlize' in template files (.html) and grep for 'urlize' in view code that passes data to templatesAffected if Templates use the urlize filter on any user-supplied data
-
Identify usage of urlizetrunc template filterSearch your codebase for '|urlizetrunc' in template files (.html) and grep for 'urlizetrunc' in view codeAffected if Templates use the urlizetrunc filter on any user-supplied data
-
Determine if untrusted input reaches these filtersReview the data flow from HTTP requests through views to templates: check if request.GET, request.POST, or database content containing user input is rendered through urlize/urlizetruncAffected if User-generated content (comments, posts, profile fields, search queries) is passed directly to these filters without length validation
You are affected if your Django version falls within the vulnerable ranges AND your templates use urlize or urlizetrunc on untrusted user-supplied input that could contain specially crafted large strings.
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.165.0.9
Upgrade Django to version 5.1.1, 5.0.9, or 4.2.16 or later. Until patched, avoid using urlize() and urlizetrunc() on untrusted user input or implement input length limits.
Django 4.2.16, 5.0.9, or 5.1.1 (depending on your current major.minor version)
- Identify your current Django version using 'django --version' or checking requirements.txt
- For Django 4.2.x: Upgrade to 4.2.16 or later by running: pip install 'Django>=4.2.16'
- For Django 5.0.x: Upgrade to 5.0.9 or later by running: pip install 'Django>=5.0.9'
- For Django 5.1.x: Upgrade to 5.1.1 or later by running: pip install 'Django>=5.1.1'
- After upgrading, verify the new version with 'django --version'
- Test your application to ensure the urlize() and urlizetrunc() template filters work correctly with the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Django
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45230 — 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-45230 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