Django up to 3.2.24/4.2.10/5.0.2 Regular Expression django.utils.text.Truncator.words redos
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Django up to 3.2.24/4.2.10/5.0.2. It has been rated as problematic. The impacted element is the function django.utils.text.Truncator.words of the component Regular Expression Handler. The manipulation leads to redos.
This vulnerability is uniquely identified as CVE-2024-27351. No exploit exists.
Upgrading the affected component is advised.
Details
A vulnerability, which was classified as problematic, has been found in Django up to 3.2.24/4.2.10/5.0.2 (Content Management System). This issue affects the function django.utils.text.Truncator.words of the component Regular Expression Handler. The manipulation with an unknown input leads to a redos vulnerability. Using CWE to declare the problem leads to CWE-1333. The product uses a regular expression with an inefficient, possibly exponential worst-case computational complexity that consumes excessive CPU cycles. Impacted is availability.
The weakness was disclosed 03/04/2024. It is possible to read the advisory at bugzilla.redhat.com. The identification of this vulnerability is CVE-2024-27351 since 02/25/2024. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1449.003 according to MITRE ATT&CK.
The vulnerability scanner Nessus provides a plugin with the ID 211092 (Fedora 41 : python-django (2024-c5c5671edb)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 3.2.25, 4.2.11 or 5.0.3 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (211092). Be aware that VulDB is the high quality source for vulnerability data.
Product
Type
Name
Version
- 3.2.0
- 3.2.1
- 3.2.2
- 3.2.3
- 3.2.4
- 3.2.5
- 3.2.6
- 3.2.7
- 3.2.8
- 3.2.9
- 3.2.10
- 3.2.11
- 3.2.12
- 3.2.13
- 3.2.14
- 3.2.15
- 3.2.16
- 3.2.17
- 3.2.18
- 3.2.19
- 3.2.20
- 3.2.21
- 3.2.22
- 3.2.23
- 3.2.24
- 4.2.0
- 4.2.1
- 4.2.2
- 4.2.3
- 4.2.4
- 4.2.5
- 4.2.6
- 4.2.7
- 4.2.8
- 4.2.9
- 4.2.10
- 5.0.0
- 5.0.1
- 5.0.2
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: RedosCWE: CWE-1333 / CWE-400 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 211092
Nessus Name: Fedora 41 : python-django (2024-c5c5671edb)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Django 3.2.25/4.2.11/5.0.3
Timeline
02/25/2024 🔍03/04/2024 🔍
03/04/2024 🔍
10/10/2025 🔍
Sources
Advisory: bugzilla.redhat.comStatus: Confirmed
CVE: CVE-2024-27351 (🔍)
GCVE (CVE): GCVE-0-2024-27351
GCVE (VulDB): GCVE-100-255647
Entry
Created: 03/04/2024 14:23Updated: 10/10/2025 18:13
Changes: 03/04/2024 14:23 (37), 03/05/2024 09:24 (4), 04/04/2024 12:02 (15), 11/17/2024 11:21 (3), 10/10/2025 18:13 (1)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
Could you please align the "python-django:python-django" cpe to the "django:django" cpe since it is a follow up to CVE-2019-14232 and CVE-2023-43665?
We would appreciate it very much.
Best Regards,
TEAM CERT
Do you want to use VulDB in your project?
Use the official API to access entries easily!