# CVE-2020-1717: Generation of Error Message Containing Sensitive Information in Keycloak

> A logged-in user can enumerate account emails in Keycloak, exposing user data to attackers.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Feb 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-rvfc-g8j5-9ccf

## What is CVE-2020-1717?

CVE-2020-1717 is a low-severity vulnerability in Redhat Keycloak, published on 11 Feb 2021. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A flaw was found in Keycloak 7.0.1. A logged in user can do an account email enumeration attack.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

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

2 open source packages ship an affected version, including org.keycloak:keycloak-parent. It affects 4 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.keycloak:keycloak-parent` | Maven | All versions to 7.0.1 | None |
| `org.keycloak:keycloak-parent` | Maven | All versions to 7.0.1 | None |

Products: Redhat Jboss Fuse, Redhat Keycloak, Redhat Openshift Application Runtimes, Redhat Single Sign-On.

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

No fix has been published for CVE-2020-1717 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-1717 being exploited?

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

## Other vulnerabilities in Redhat Keycloak

- [CVE-2020-27782](https://insights.sbomify.com/CVE-2020-27782/): Denial of service in Undertow (high 7.5)
- [CVE-2020-10718](https://insights.sbomify.com/CVE-2020-10718/): Security feature bypass in Wildfly (high 7.5)
- [CVE-2020-1718](https://insights.sbomify.com/CVE-2020-1718/): Improper Authentication for Keycloak (high 7.1)
- [CVE-2016-1000229](https://insights.sbomify.com/CVE-2016-1000229/): Improper Neutralization of Input During Web Page Generation in swagger-ui (medium 6.1)
- [CVE-2014-8175](https://insights.sbomify.com/CVE-2014-8175/): Auth bypass in n/a (medium 6.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-1717 is a low-severity vulnerability in Redhat Keycloak, published on 11 Feb 2021. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-1717 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.keycloak:keycloak-parent (Maven): affected all versions up to 7.0.1; no fix listed
- org.keycloak:keycloak-parent (Maven): affected all versions up to 7.0.1; no fix listed

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-1717/ (Markdown: https://insights.sbomify.com/CVE-2020-1717/index.md)
```

## Sources

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

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