Django up to 3.2.19/4.1.9/4.2.2 EmailValidator/URLValidator redos
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Django up to 3.2.19/4.1.9/4.2.2. It has been rated as problematic. Affected is the function EmailValidator/URLValidator. Performing a manipulation results in redos.
This vulnerability is cataloged as CVE-2023-36053. It is possible to initiate the attack remotely. There is no exploit available.
Upgrading the affected component is advised.
Details
A vulnerability, which was classified as problematic, was found in Django up to 3.2.19/4.1.9/4.2.2 (Content Management System). This affects the function EmailValidator/URLValidator. The manipulation with an unknown input leads to a redos vulnerability. CWE is classifying the issue as CWE-1333. The product uses a regular expression with an inefficient, possibly exponential worst-case computational complexity that consumes excessive CPU cycles. This is going to have an impact on availability.
The weakness was shared 07/03/2023. The advisory is shared at seclists.org. This vulnerability is uniquely identified as CVE-2023-36053 since 06/20/2023. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1449.003 for this issue.
Upgrading to version 3.2.20, 4.1.10 or 4.2.3 eliminates this vulnerability. The upgrade is hosted for download at docs.djangoproject.com.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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
- 4.1.0
- 4.1.1
- 4.1.2
- 4.1.3
- 4.1.4
- 4.1.5
- 4.1.6
- 4.1.7
- 4.1.8
- 4.1.9
- 4.2.0
- 4.2.1
- 4.2.2
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: RedosCWE: CWE-1333 / 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.20/4.1.10/4.2.3
Timeline
06/20/2023 🔍07/03/2023 🔍
07/03/2023 🔍
07/22/2023 🔍
Sources
Advisory: DLA 3500-1Status: Confirmed
CVE: CVE-2023-36053 (🔍)
GCVE (CVE): GCVE-0-2023-36053
GCVE (VulDB): GCVE-100-232869
Entry
Created: 07/03/2023 14:00Updated: 07/22/2023 15:48
Changes: 07/03/2023 14:00 (39), 07/22/2023 15:43 (2), 07/22/2023 15:48 (11)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.