Django: Improper Validation of Specified Quantity in Input
CVE-2023-41164 is a high-severity improper validation of specified quantity in input 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 3.2.21, 4.1.11, 4.2.5 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.52% chance of exploitation within 30 days, higher than 75% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Django to 3.2.21 or 4.1.11 or 4.2.5, whichever matches your release line, or a later version.
- Read the advisory on docs.djangoproject.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Django | Django | 3.2 up to, but not including, 3.2.21; 4.1 up to, but not including, 4.1.11; 4.2 up to, but not including, 4.2.5 | 3.2.21, 4.1.11, 4.2.5 |
| Fedora Project | Fedora | 39 | Not stated |
Version data comes from NVD's product matching. 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.
Official description
In Django 3.2 before 3.2.21, 4.1 before 4.1.11, and 4.2 before 4.2.5, django.utils.encoding.uri_to_iri() is subject to a potential DoS (denial of service) attack via certain inputs with a very large number of Unicode characters.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Validation of Specified Quantity in Input
The product receives input that is expected to specify a quantity (such as size or length), but it does not validate or incorrectly validates that the quantity has the required properties.
More Improper Validation of Specified Quantity in Input vulnerabilities (CWE-1284)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Advisories
Third-party and government advisories
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HJFRPUHDYJHBH3KYHSPG…Mailing List, Third Party Advisory
Other references
- groups.google.com/forum/#%21forum/django-announcePermissions Required
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZQJOMNRMVPCN5WMIZ7YS…
- security.netapp.com/advisory/ntap-20231214-0002/
- lists.fedoraproject.org/archives/list/[email protected]/message/ZQJOMNRMVPCN5WMIZ7YSX5…
Other vulnerabilities in Django
- 8.8 High severity
- 9.8 Critical severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 8.5 High severity
Recent Improper Validation of Specified Quantity in Input vulnerabilities
- 7.5 High severity
- 8.1 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 8.8 High severity
Spotted an error? Tell us.