Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2020-1725 | First vendor Publication | 2021-01-28 |
Vendor | Cve | Last vendor Modification | 2024-11-21 |
Security-Database Scoring CVSS v3
Cvss vector : CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N | |||
---|---|---|---|
Overall CVSS Score | 5.4 | ||
Base Score | 5.4 | Environmental Score | 5.4 |
impact SubScore | 2.5 | Temporal Score | 5.4 |
Exploitabality Sub Score | 2.8 | ||
Attack Vector | Network | Attack Complexity | Low |
Privileges Required | Low | User Interaction | None |
Scope | Unchanged | Confidentiality Impact | Low |
Integrity Impact | Low | Availability Impact | None |
Calculate full CVSS 3.0 Vectors scores |
Security-Database Scoring CVSS v2
Cvss vector : (AV:N/AC:L/Au:S/C:P/I:P/A:N) | |||
---|---|---|---|
Cvss Base Score | 5.5 | Attack Range | Network |
Cvss Impact Score | 4.9 | Attack Complexity | Low |
Cvss Expoit Score | 8 | Authentication | Requires single instance |
Calculate full CVSS 2.0 Vectors scores |
Detail
A flaw was found in keycloak before version 13.0.0. In some scenarios a user still has access to a resource after changing the role mappings in Keycloak and after expiration of the previous access token. |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1725 |
CPE : Common Platform Enumeration
Sources (Detail)
Source | Url |
---|
Alert History
Date | Informations |
---|---|
2024-11-28 13:40:56 |
|
2022-08-27 01:51:04 |
|
2022-04-14 01:43:26 |
|
2021-05-05 01:39:15 |
|
2021-05-04 13:51:05 |
|
2021-04-22 03:02:38 |
|
2021-03-31 17:22:51 |
|
2021-03-26 21:23:10 |
|
2021-02-03 21:23:25 |
|
2021-01-29 00:22:51 |
|