creditease-sec insight up to 2018-09-11 srcpm/app/admin/views.py depart_delete cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in creditease-sec insight up to 2018-09-11. It has been rated as problematic. Affected is the function depart_delete of the file srcpm/app/admin/views.py. This manipulation causes cross-site request forgery.
This vulnerability is tracked as CVE-2019-6509. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability classified as problematic was found in creditease-sec insight up to 2018-09-11. Affected by this vulnerability is the function depart_delete of the file srcpm/app/admin/views.py. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. The CWE definition for the vulnerability is CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. As an impact it is known to affect integrity. The summary by CVE is:
An issue was discovered in creditease-sec insight through 2018-09-11. depart_delete in srcpm/app/admin/views.py allows CSRF.
The bug was discovered 01/22/2019. The weakness was disclosed 01/22/2019 (Website). The advisory is shared at github.com. This vulnerability is known as CVE-2019-6509 since 01/22/2019. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-129995, VDB-129996 and VDB-129998 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.6VulDB Meta Temp Score: 6.6
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Cross-site request forgeryCWE: CWE-352 / CWE-862 / CWE-863
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
01/22/2019 🔍01/22/2019 🔍
01/22/2019 🔍
01/22/2019 🔍
01/22/2019 🔍
07/02/2023 🔍
Sources
Advisory: 42Status: Not defined
CVE: CVE-2019-6509 (🔍)
GCVE (CVE): GCVE-0-2019-6509
GCVE (VulDB): GCVE-100-129997
See also: 🔍
Entry
Created: 01/22/2019 21:53Updated: 07/02/2023 10:26
Changes: 01/22/2019 21:53 (56), 05/04/2020 14:18 (1), 07/02/2023 10:26 (3)
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.