CVE-2020-1744 — keycloak-core
MEDIUMCVE-2020-1744 is a medium-severity (CVSS 5.6) CWE-755 vulnerability in org.keycloak:keycloak-core. A fix is available for org.keycloak:keycloak-core — see the affected versions and patch details below.
Exposure of Sensitive Information in keycloak
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2020-1744 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,386 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-coreReal-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 keycloak before version 9.0.1. When configuring an Conditional OTP Authentication Flow as a post login flow of an IDP, the failure login events for OTP are not being sent to the brute force protection event queue. So BruteForceProtector does not handle this events.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.keycloak:keycloak-core | all versions | 9.0.1org.keycloak:keycloak-core:9.0.1 |
Affected Products
keycloakredhatDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.keycloak:keycloak-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.keycloak:keycloak-core to 9.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-1744 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
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.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Runtimes Spring Boot 2.2.6 | keycloak | RHSA-2020:2252 |
| Red Hat Single Sign-On 7.3 | see advisory | RHSA-2020:0951 |
| Red Hat Single Sign-On 7.3 for RHEL 6 | rh-sso7-keycloak-0:4.8.18-1.Final_redhat_00001.1.el6sso | RHSA-2020:0945 |
| Red Hat Single Sign-On 7.3 for RHEL 7 | rh-sso7-keycloak-0:4.8.18-1.Final_redhat_00001.1.el7sso | RHSA-2020:0946 |
| Red Hat Single Sign-On 7.3 for RHEL 8 | rh-sso7-keycloak-0:4.8.18-1.Final_redhat_00001.1.el8sso | RHSA-2020:0947 |
| Text-Only RHOAR | see advisory | RHSA-2020:2905 |
Frequently Asked Questions
Is CVE-2020-1744 in your dependencies?
Find it across Maven, including transitive dependencies.