# CVE-2020-1744: Exposure of Sensitive Information in keycloak

> Attackers can bypass brute force protection in Keycloak when using Conditional OTP in IDP post-login flows, allowing unlimited login attempts.

- **Severity:** Medium 5.6 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-4gf2-xv97-63m2, RHSA-2020:0945, RHSA-2020:0946, RHSA-2020:0947

## What is CVE-2020-1744?

CVE-2020-1744 is a medium-severity vulnerability in Redhat Keycloak, published on 24 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-755 (Improper Handling of Exceptional Conditions)

## Which versions are affected by CVE-2020-1744?

2 open source packages ship an affected version, including org.keycloak:keycloak-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.keycloak:keycloak-core` | Maven | All versions | 9.0.1 |
| `org.keycloak:keycloak-core` | Maven | All versions | 9.0.1 |
| `rh-sso7-keycloak` | Red Hat:red_hat_single_sign_on:7::el6 | All versions | 0:4.8.18-1.Final_redhat_00001.1.el6sso |
| `rh-sso7-keycloak-server` | Red Hat:red_hat_single_sign_on:7::el6 | All versions | 0:4.8.18-1.Final_redhat_00001.1.el6sso |
| `rh-sso7-keycloak` | Red Hat:red_hat_single_sign_on:7::el7 | All versions | 0:4.8.18-1.Final_redhat_00001.1.el7sso |
| `rh-sso7-keycloak-server` | Red Hat:red_hat_single_sign_on:7::el7 | All versions | 0:4.8.18-1.Final_redhat_00001.1.el7sso |
| `rh-sso7-keycloak` | Red Hat:red_hat_single_sign_on:7::el8 | All versions | 0:4.8.18-1.Final_redhat_00001.1.el8sso |
| `rh-sso7-keycloak-server` | Red Hat:red_hat_single_sign_on:7::el8 | All versions | 0:4.8.18-1.Final_redhat_00001.1.el8sso |

Products: Redhat Keycloak.

## How do I fix CVE-2020-1744?

Upgrade org.keycloak:keycloak-core to 9.0.1 or later.

## Is CVE-2020-1744 being exploited?

There is no known exploitation of CVE-2020-1744 in the wild and no public exploit code.

## Other vulnerabilities in Redhat Keycloak

- [CVE-2022-4361](https://insights.sbomify.com/CVE-2022-4361/): Keycloak vulnerable to cross-site scripting when validating URI-schemes on SAML and OIDC (critical 10.0)
- [CVE-2022-1245](https://insights.sbomify.com/CVE-2022-1245/): Keycloak vulnerable to privilege escalation on Token Exchange feature (critical 9.8)
- [CVE-2021-20195](https://insights.sbomify.com/CVE-2021-20195/): keycloak Self Stored Cross-site Scripting vulnerability (critical 9.6)
- [CVE-2019-14910](https://insights.sbomify.com/CVE-2019-14910/): Keycloak Authentication Error (critical 9.3)
- [CVE-2019-14909](https://insights.sbomify.com/CVE-2019-14909/): Keycloak Authentication Error (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-1744 and fix it if it is affected.

What it is: CVE-2020-1744 is a medium-severity vulnerability in Redhat Keycloak, published on 24 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-1744 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.keycloak:keycloak-core (Maven): affected all versions; fixed in 9.0.1
- org.keycloak:keycloak-core (Maven): affected all versions; fixed in 9.0.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-1744/ (Markdown: https://insights.sbomify.com/CVE-2020-1744/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-1744
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-1744
- OSV: https://osv.dev/vulnerability/CVE-2020-1744

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-1744/
Summaries are generated and may contain mistakes; the official description above is the record.