Django prior 3.2.17/4.0.9/4.1.6 Header Accept-Language allocation of resources
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.8 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Django. Impacted is an unknown function of the component Header Handler. The manipulation of the argument Accept-Language leads to allocation of resources. This vulnerability is listed as CVE-2023-23969. The attack may be initiated remotely. There is no available exploit. It is advisable to upgrade the affected component.
Details
A vulnerability was found in Django (Content Management System) and classified as problematic. This issue affects an unknown functionality of the component Header Handler. The manipulation of the argument Accept-Language with an unknown input leads to a allocation of resources vulnerability. Using CWE to declare the problem leads to CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. Impacted is availability. The summary by CVE is:
In Django 3.2 before 3.2.17, 4.0 before 4.0.9, and 4.1 before 4.1.6, the parsed values of Accept-Language headers are cached in order to avoid repetitive parsing. This leads to a potential denial-of-service vector via excessive memory usage if the raw value of Accept-Language headers is very large.
The weakness was presented 02/01/2023. It is possible to read the advisory at docs.djangoproject.com. The identification of this vulnerability is CVE-2023-23969 since 01/20/2023. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1499 according to MITRE ATT&CK.
Upgrading to version 3.2.17, 4.0.9 or 4.1.6 eliminates this vulnerability. The upgrade is hosted for download at docs.djangoproject.com.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-0066). Be aware that VulDB is the high quality source for vulnerability data.
Product
Type
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.8
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Allocation of resourcesCWE: CWE-770 / CWE-400 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Django 3.2.17/4.0.9/4.1.6
Timeline
01/20/2023 🔍02/01/2023 🔍
02/01/2023 🔍
07/01/2025 🔍
Sources
Advisory: DLA 3306-1Status: Confirmed
Confirmation: 🔍
CVE: CVE-2023-23969 (🔍)
GCVE (CVE): GCVE-0-2023-23969
GCVE (VulDB): GCVE-100-219983
EUVD: 🔍
Entry
Created: 02/01/2023 20:58Updated: 07/01/2025 14:12
Changes: 02/01/2023 20:58 (42), 03/01/2023 14:23 (1), 03/01/2023 14:26 (11), 07/01/2025 14:12 (16)
Complete: 🔍
Cache ID: 216:00A:103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.