CVE-2020-1718 — keycloak-parent
HIGHCVE-2020-1718 is a high-severity (CVSS 8.8) Improper Authentication vulnerability in org.keycloak:keycloak-parent. A fix is available for org.keycloak:keycloak-parent — see the affected versions and patch details below.
Improper Authentication for Keycloak
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2020-1718 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.keycloak:keycloak-parentReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.keycloak:keycloak-parent | all versions | 8.0.0org.keycloak:keycloak-parent:8.0.0 |
Affected Products
jboss fuseredhatkeycloakredhatopenshift application runtimesredhatDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.keycloak:keycloak-parent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.keycloak:keycloak-parent to 8.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-1718 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Disable reset credential flow.Source: Red Hat security advisory for CVE-2020-1718 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Decision Manager 7 | keycloak | RHSA-2020:3196 |
| Red Hat Process Automation 7 | keycloak | RHSA-2020:3197 |
| Red Hat Runtimes Spring Boot 2.2.6 | keycloak | RHSA-2020:2252 |
| Red Hat Single Sign On 7.3.8 | see advisory | RHSA-2020:2112 |
| Red Hat Single Sign-On 7.3 for RHEL 6 | rh-sso7-keycloak-0:4.8.20-1.Final_redhat_00001.1.el6sso | RHSA-2020:2106 |
| Red Hat Single Sign-On 7.3 for RHEL 7 | rh-sso7-keycloak-0:4.8.20-1.Final_redhat_00001.1.el7sso | RHSA-2020:2107 |
| Red Hat Single Sign-On 7.3 for RHEL 8 | rh-sso7-keycloak-0:4.8.20-1.Final_redhat_00001.1.el8sso | RHSA-2020:2108 |
| Text-Only RHOAR | see advisory | RHSA-2020:2905 |
Frequently Asked Questions
Is CVE-2020-1718 in your dependencies?
Find it across Maven, including transitive dependencies.