django is vulnerable to Denial of Service (DoS)
50
CVE Score
Medium
Denial of Service (DoS)
Django's django.utils.http.parse_header_parameters() parsed Content-Type-like header values (such as Accept or Content-Type) using a custom _parseparam() generator that rescanned the remaining string for the next unescaped semicolon on every iteration, giving quadratic time complexity when a quoted parameter value contained many semicolon separators. An unauthenticated attacker could trigger this parsing path via ordinary HTTP headers processed during content negotiation (e.g. HttpRequest.accepts()), and the existing MAX_HEADER_LENGTH per-call limit did not bound the cost of repeated headers, enabling a denial-of-service. The fix replaces the custom parser with Python's email.message.Message-based parameter parsing, eliminating the quadratic rescanning behavior.
Upgrade the django library to the patch version.
You are affected if you are using a version that falls within the vulnerable range and you parse request headers such as Accept or Content-Type through parse_header_parameters() or HttpRequest.accepts().
5.2 - 5.2.17
Fixed in 5.2.186.0 - 6.0.8
Fixed in 6.0.96.1 - 6.1.1
Fixed in 6.1.2django is vulnerable to Denial of Service (DoS) in versions 6.1 - 6.1.1, 6.0 - 6.0.8 and 5.2 - 5.2.17.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.