Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2020-5251 | First vendor Publication | 2020-03-04 |
Vendor | Cve | Last vendor Modification | 2024-11-21 |
Security-Database Scoring CVSS v3
Cvss vector : CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N | |||
---|---|---|---|
Overall CVSS Score | 5.3 | ||
Base Score | 5.3 | Environmental Score | 5.3 |
impact SubScore | 1.4 | Temporal Score | 5.3 |
Exploitabality Sub Score | 3.9 | ||
Attack Vector | Network | Attack Complexity | Low |
Privileges Required | None | User Interaction | None |
Scope | Unchanged | Confidentiality Impact | Low |
Integrity Impact | None | Availability Impact | None |
Calculate full CVSS 3.0 Vectors scores |
Security-Database Scoring CVSS v2
Cvss vector : (AV:N/AC:L/Au:N/C:P/I:N/A:N) | |||
---|---|---|---|
Cvss Base Score | 5 | Attack Range | Network |
Cvss Impact Score | 2.9 | Attack Complexity | Low |
Cvss Expoit Score | 10 | Authentication | None Required |
Calculate full CVSS 2.0 Vectors scores |
Detail
In parser-server before version 4.1.0, you can fetch all the users objects, by using regex in the NoSQL query. Using the NoSQL, you can use a regex on sessionToken and find valid accounts this way. |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-5251 |
CPE : Common Platform Enumeration
Type | Description | Count |
---|---|---|
Application | 2 |
Sources (Detail)
Source | Url |
---|
Alert History
Date | Informations |
---|---|
2024-11-28 13:45:58 |
|
2021-05-04 13:54:47 |
|
2021-04-22 03:05:26 |
|
2021-01-05 12:31:43 |
|
2020-05-23 02:36:59 |
|