Django REST Framework up to 3.9.0 DRF Browsable API cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.7 | $0-$5k | 0.86 |
Summary
A vulnerability has been found in Django REST Framework up to 3.9.0 and classified as problematic. Affected by this vulnerability is an unknown functionality of the component DRF Browsable API. Performing a manipulation results in cross site scripting. This vulnerability was named CVE-2018-25045. The attack may be initiated remotely. There is no available exploit. The affected component should be upgraded.
Details
A vulnerability was found in Django REST Framework up to 3.9.0 (Content Management System). It has been classified as problematic. This affects an unknown part of the component DRF Browsable API. The manipulation with an unknown input leads to a cross site scripting vulnerability. CWE is classifying the issue as CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. This is going to have an impact on integrity. The summary by CVE is:
Django REST framework (aka django-rest-framework) before 3.9.1 allows XSS because the default DRF Browsable API view templates disable autoescaping.
The weakness was presented 07/23/2022. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2018-25045 since 07/23/2022. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1059.007 according to MITRE ATT&CK.
Upgrading to version 3.9.1 eliminates this vulnerability. Applying the patch 4bb9a3c48427867ef1e46f7dee945a4c25a4f9b8 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.8VulDB Meta Temp Score: 4.7
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.1
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: Cross site scriptingCWE: CWE-79 / CWE-94 / CWE-74
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 REST Framework 3.9.1
Patch: 4bb9a3c48427867ef1e46f7dee945a4c25a4f9b8
Timeline
07/23/2022 🔍07/23/2022 🔍
07/23/2022 🔍
08/20/2022 🔍
Sources
Advisory: 4bb9a3c48427867ef1e46f7dee945a4c25a4f9b8Status: Confirmed
CVE: CVE-2018-25045 (🔍)
GCVE (CVE): GCVE-0-2018-25045
GCVE (VulDB): GCVE-100-204963
Entry
Created: 07/23/2022 15:08Updated: 08/20/2022 14:49
Changes: 07/23/2022 15:08 (42), 08/20/2022 14:45 (1), 08/20/2022 14:49 (11)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.