CyberSecBulletin
CVE-2024-41990NVD status: Modified

django: Improper Handling of Length Parameter Inconsistency

Published Updated By the CyberSecBulletin desk

CVE-2024-41990 is a high-severity improper handling of length parameter inconsistency vulnerability in django, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 4.2.15, 5.0.8, pkg:pypi/[email protected] as the first without the flaw, so updating django to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.26% chance of exploitation within 30 days, higher than 70% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update django to 4.2.15 or 5.0.8 or pkg:pypi/[email protected] or pkg:pypi/[email protected], whichever matches your release line, or a later version.
  2. Read the advisory on docs.djangoproject.com for workarounds and exact fixed builds.
  3. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
Djangodjango4.2 up to, but not including, 4.2.15; 5.0 up to, but not including, 5.0.8; pkg:pypi/[email protected] up to, but not including, pkg:pypi/[email protected]; pkg:pypi/[email protected] up to, but not including, pkg:pypi/[email protected]4.2.15, 5.0.8, pkg:pypi/[email protected], pkg:pypi/[email protected]

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
NoneNo data is disclosed.
Integrity
NoneNothing can be modified.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.17.5HighNVD
CVSS 3.17.5HighCISA (ADP)

Official description

An issue was discovered in Django 5.0 before 5.0.8 and 4.2 before 4.2.15. 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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Handling of Length Parameter Inconsistency

The product parses a formatted message or structure, but it does not handle or incorrectly handles a length field that is inconsistent with the actual length of the associated data.

How developers prevent this class of flaw

  • When processing structured incoming data containing a size field followed by raw data, ensure that you identify and resolve any inconsistencies between the size field and the actual size of the data.
  • Do not let the user control the size of the buffer.
  • Validate that the length of the user-supplied data is consistent with the buffer size.

More Improper Handling of Length Parameter Inconsistency vulnerabilities (CWE-130)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in django

All django vulnerabilities

Recent Improper Handling of Length Parameter Inconsistency vulnerabilities

Spotted an error? Tell us.