CVE-2020-1718 json
Improper Authentication for Keycloak
published 6y ago modified 4mo ago also GHSA-j229-2h63-rvh9 , EUVD-2022-1060
- cvss
- 7.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 63%
- public exploits
- 0
- none known
Summary
A flaw was found in the reset credential flow in all Keycloak versions before 8.0.0. This flaw allows an attacker to gain unauthorized access to the application.
Patch / fix
- maven org.keycloak:keycloak-parent 8.0.0
- redhat keycloak 8.0.0
- rh-sso7-keycloak red hat single sign on 7 4.8.20-1.Final_redhat_00001.1.el8sso
- rh-sso7-keycloak-server red hat single sign on 7 4.8.20-1.Final_redhat_00001.1.el8sso
- rh-sso7-keycloak red hat single sign on 7 4.8.20-1.Final_redhat_00001.1.el7sso
- rh-sso7-keycloak-server red hat single sign on 7 4.8.20-1.Final_redhat_00001.1.el7sso
- rh-sso7-keycloak red hat single sign on 7 4.8.20-1.Final_redhat_00001.1.el6sso
- rh-sso7-keycloak-server red hat single sign on 7 4.8.20-1.Final_redhat_00001.1.el6sso
red hat advisories RHSA-2020:2108RHSA-2020:2107RHSA-2020:2106
Is CVE-2020-1718 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2020-1718 updated cvss 8.8
keycloak: security issue on reset credential flow
-
Red Hat OpenShift Application Runtimes keycloak keycloak Red Hat support for Spring Boot keycloak keycloakaffected: workaround, no fix available “Disable reset credential flow.”
-
Red Hat Decision Manager 7fixed: vendor fix “Disable reset credential flow.” RHSA-2020:3196
-
Red Hat Process Automation 7fixed: vendor fix “Disable reset credential flow.” RHSA-2020:3197
-
Red Hat Runtimes Spring Boot 2.2.6fixed: vendor fix “Disable reset credential flow.” RHSA-2020:2252
-
Red Hat Single Sign On 7.3.8fixed: vendor fix “Disable reset credential flow.” RHSA-2020:2112
-
Red Hat Single Sign-On 7.3 for RHEL 6 Server rh-sso7-keycloak 4.8.20-1.Final_redhat_00001.1.el6sso, rh-sso7-keycloak-server 4.8.20-1.Final_redhat_00001.1.el6ssofixed: vendor fix “Disable reset credential flow.” RHSA-2020:2106
-
Red Hat Single Sign-On 7.3 for RHEL 7 Server rh-sso7-keycloak 4.8.20-1.Final_redhat_00001.1.el7sso, rh-sso7-keycloak-server 4.8.20-1.Final_redhat_00001.1.el7ssofixed: vendor fix “Disable reset credential flow.” RHSA-2020:2107
-
Red Hat Single Sign-On 7.3 for RHEL 8 rh-sso7-keycloak 4.8.20-1.Final_redhat_00001.1.el8sso, rh-sso7-keycloak-server 4.8.20-1.Final_redhat_00001.1.el8ssofixed: vendor fix “Disable reset credential flow.” RHSA-2020:2108
show 2 moreshow fewer
-
Red Hat Text-Only RHOARfixed: vendor fix “Disable reset credential flow.” RHSA-2020:2905
-
Red Hat Fuse 7 keycloak keycloaknot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.00% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.1 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:H |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
| GitHub | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.keycloak:keycloak-parent | <8.0.0 |
8.0.0 |
Affected products
- Red Hat keycloak
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
-
bugzilla.redhat.com
/show_bug.cgi?id=CVE-2020-1718
web, issue-tracking, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-1718
advisory
Sources
- CVE List CVE-2020-1718
- GitHub Advisory GHSA-j229-2h63-rvh9
- NVD CVE-2020-1718
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.